From: "Wiles, Keith" <keith.wiles@intel.com>
To: Pascal Mazon <pascal.mazon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/tap: support segmented mbufs
Date: Wed, 15 Mar 2017 21:47:26 +0000 [thread overview]
Message-ID: <95576E63-F346-4B17-8C9C-C9FE0303EC75@intel.com> (raw)
In-Reply-To: <74ac5afc58ae941184f3886c5eeb9fbc8b5d9c9d.1489590563.git.pascal.mazon@6wind.com>
> On Mar 15, 2017, at 11:09 PM, Pascal Mazon <pascal.mazon@6wind.com> wrote:
>
> Support for segmented packets (scatter/gather) is mandatory for most
> purposes, regardless of the MTU size. Tx packets are often the result of
> mbuf concatenation, and an mbuf is not necessarily large enough for Rx
> packets to fit in a single one.
>
> Signed-off-by: Pascal Mazon <pascal.mazon@6wind.com>
Ack-by: Keith.Wiles@intel.com
> ---
> drivers/net/tap/rte_eth_tap.c | 176 +++++++++++++++++++++++++++++++++++-------
> drivers/net/tap/rte_eth_tap.h | 10 +++
> 2 files changed, 157 insertions(+), 29 deletions(-)
Regards,
Keith
next prev parent reply other threads:[~2017-03-15 21:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 15:09 Pascal Mazon
2017-03-15 21:47 ` Wiles, Keith [this message]
2017-03-16 8:59 ` [dpdk-dev] [PATCH v2] " Pascal Mazon
2017-03-24 15:38 ` Ferruh Yigit
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=95576E63-F346-4B17-8C9C-C9FE0303EC75@intel.com \
--to=keith.wiles@intel.com \
--cc=dev@dpdk.org \
--cc=pascal.mazon@6wind.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).