From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Yutaro Hayakawa <yhayakawa3720@gmail.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] AF_XDP PMD cannot use with software NICs
Date: Tue, 28 May 2019 10:40:09 +0100 [thread overview]
Message-ID: <c778a821-4874-0523-6d5c-a929941e3dfc@intel.com> (raw)
In-Reply-To: <678FFC0B-20D6-4913-AF2B-CB08A10F5A7E@gmail.com>
On 25-May-19 1:45 AM, Yutaro Hayakawa wrote:
> Hello,
>
> In current AF_XDP PMD implementation, we cannot use it with software NICs like 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 useful for testing perpose or using DPDK from containers.
I'm not sure i understand the problem. IOVA_CONTIG has no relation to
SIZE_HINT_ONLY - the former forces the allocation to be IOVA-contiguous.
The latter allows to allocate from other page sizes when the requested
one is not available, e.g. if you request memory with RTE_MEMZONE_1GB
and RTE_MEMZONE_SIZE_HINT_ONLY, it will try to allocate from 1GB pages
first, and if that fails, will allocate from any other page size
available - but says nothing about whether that memory has to be
IOVA-contiguous.
What is the problem with allocating IOVA-contiguous memory for AF_XDP
and VETH?
>
> Any thought or future plan for this problem?
>
> Thanks,
> Yutaro
>
--
Thanks,
Anatoly
prev parent reply other threads:[~2019-05-28 9:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-25 0:45 [dpdk-dev] AF_XDP PMD cannot use with software NICs Yutaro Hayakawa
2019-05-28 9:40 ` Burakov, Anatoly [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c778a821-4874-0523-6d5c-a929941e3dfc@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=yhayakawa3720@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).