From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=3.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id DB423C282E1 for ; Sat, 25 May 2019 00:45:43 +0000 (UTC) Received: from dpdk.org (dpdk.org [92.243.14.124]) by mail.kernel.org (Postfix) with ESMTP id 83AC6217D7 for ; Sat, 25 May 2019 00:45:43 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="s7amTk24" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 83AC6217D7 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=dev-bounces@dpdk.org Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 49F66A69; Sat, 25 May 2019 02:45:42 +0200 (CEST) Received: from mail-pg1-f174.google.com (mail-pg1-f174.google.com [209.85.215.174]) by dpdk.org (Postfix) with ESMTP id 306AAA49 for ; Sat, 25 May 2019 02:45:41 +0200 (CEST) Received: by mail-pg1-f174.google.com with SMTP id h2so2851613pgg.1 for ; Fri, 24 May 2019 17:45:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:date:subject:message-id :to; bh=VQq7bd9iLjKH7ehejLjB+XqanpBGyPuiHM9Z3vVB8gY=; b=s7amTk24ZXVAuMh6SsmpeVaKTzRzoKOAT2k9swN6a4NqSUi6J0gnXxbbqZZdvLs1iA qC50yo9OS2xOhtDW1nQQT/NaNPJCEW/IWnY7sE97f5ptk2777EeFdd2n8+ig7phkha5+ qsqGw1rPOU+fak3t3l9Mn+gPbyYIUpR5c3XZOAEdmwEibs9bvX0/s/RCIWppFJMoMbZ5 dtf9f+q/J9KpVD+ZIVuEN1h/b+A1TSFpCiBvkT0TiI9+/YkY7Wq5b7mdJELVojTpydZZ 5RmQ7POnBKBtau/r/am0+fWBTYIZFfzej0zTUg/CMxqxxYZLEiGEIRUhfOXaYzi8aQpc KSEA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version:date :subject:message-id:to; bh=VQq7bd9iLjKH7ehejLjB+XqanpBGyPuiHM9Z3vVB8gY=; b=s3b++7V45LZ4NqpKtOUMdPYCCestpTQbJUQ4iB86Qj3hrssXOFifR40TcRRVoIIYOx 2R7hb5Bc0AAgLxiP1pANIVopfZWePvmEIHDKH5zyr+9EUl9o3DKZzzS3xduf+PlfrQwu PCyXxv1CgfwdwEpNyvUCm7W3hXhHANcbZqlff2zsHxMZFW3RFm45JxHnh+aQ3Hgk9VJz CjiCom6Fxf7IyyBJxk73wSaeT/LXsCBPT2H9w0mU96QaRTdjhA1Es9J/8rtonkBVw03Z 7HfFsZZuLKXqdg/7rJROHz5ZuMlQuOmlWbaz0BJWtG71qPgJtpvgek/ckNxKrqx8ue+U kpeA== X-Gm-Message-State: APjAAAVLg+37jLXu8Js53UR+h10kgZV5kJv5R+TVbm5j8RPPLWHyVzIg +AgV3GwX2ywsPnCIiABUlvlAL3iU X-Google-Smtp-Source: APXvYqw4TCERnVo9e35es/hEy3PnQgFItuh7zbQxNnNdEJ4PoEx6/4h70LMfMsW78NTBul5fu/0KFA== X-Received: by 2002:aa7:8dd6:: with SMTP id j22mr52642394pfr.192.1558745140203; Fri, 24 May 2019 17:45:40 -0700 (PDT) Received: from [122.29.73.246] (p901247-li-mobac01.osaka.ocn.ne.jp. [122.29.73.246]) by smtp.gmail.com with ESMTPSA id r4sm2992729pjd.25.2019.05.24.17.45.39 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 24 May 2019 17:45:39 -0700 (PDT) From: Yutaro Hayakawa Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Date: Sat, 25 May 2019 09:45:37 +0900 Message-Id: <678FFC0B-20D6-4913-AF2B-CB08A10F5A7E@gmail.com> To: dev@dpdk.org X-Mailer: iPhone Mail (16D57) Subject: [dpdk-dev] AF_XDP PMD cannot use with software NICs X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hello, In current AF_XDP PMD implementation, we cannot use it with software NICs li= ke VETH. Because it allocates umem with RTE_MEMZONE_IOVA_CONTIG. Since AF_XDP itself is usable with any network devices, I think it is better= to have option to take umem with RTE_MEMZONE_SIZE_HINT_ONLY. It is also use= ful for testing perpose or using DPDK from containers. Any thought or future plan for this problem? Thanks, Yutaro=