From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Pascal Mazon <pascal.mazon@6wind.com>, keith.wiles@intel.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] net/tap: support segmented mbufs
Date: Fri, 24 Mar 2017 15:38:43 +0000 [thread overview]
Message-ID: <fd0eae5e-6ce4-015b-6b51-d87a50163e5c@intel.com> (raw)
In-Reply-To: <d5a740a02a5d0317907257bb1a04888e18664aa3.1489654754.git.pascal.mazon@6wind.com>
On 3/16/2017 8:59 AM, Pascal Mazon 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>
> Acked-by: Keith Wiles <keith.wiles@intel.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2017-03-24 15:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 15:09 [dpdk-dev] [PATCH] " Pascal Mazon
2017-03-15 21:47 ` Wiles, Keith
2017-03-16 8:59 ` [dpdk-dev] [PATCH v2] " Pascal Mazon
2017-03-24 15:38 ` Ferruh Yigit [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=fd0eae5e-6ce4-015b-6b51-d87a50163e5c@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=keith.wiles@intel.com \
--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).