From: Yuanhan Liu <yliu@fridaylinux.org>
To: Jiayu Hu <jiayu.hu@intel.com>, Olivier MATZ <olivier.matz@6wind.com>
Cc: dev@dpdk.org, jianfeng.tan@intel.com
Subject: Re: [dpdk-dev] [PATCH] vhost: support UDP Fragmentation Offload
Date: Wed, 27 Dec 2017 22:34:54 +0800 [thread overview]
Message-ID: <20171227143454.GH8818@yliu-mob> (raw)
In-Reply-To: <1511247412-130965-1-git-send-email-jiayu.hu@intel.com>
On Tue, Nov 21, 2017 at 02:56:52PM +0800, Jiayu Hu wrote:
> In virtio, UDP Fragmentation Offload (UFO) includes two parts: host UFO
> and guest UFO. Guest UFO means the frontend can receive large UDP packets,
> and host UFO means the backend can receive large UDP packets. This patch
> supports host UFO and guest UFO for vhost-user.
>
> Signed-off-by: Jiayu Hu <jiayu.hu@intel.com>
> ---
> lib/librte_mbuf/rte_mbuf.h | 7 +++++++
> lib/librte_vhost/vhost.h | 2 ++
> lib/librte_vhost/virtio_net.c | 10 ++++++++++
> 3 files changed, 19 insertions(+)
>
> diff --git a/lib/librte_mbuf/rte_mbuf.h b/lib/librte_mbuf/rte_mbuf.h
> index ce8a05d..3d8cfc9 100644
> --- a/lib/librte_mbuf/rte_mbuf.h
> +++ b/lib/librte_mbuf/rte_mbuf.h
> @@ -209,6 +209,13 @@ extern "C" {
> /* add new TX flags here */
>
> /**
> + * UDP Fragmentation Offload flag. This flag is used for enabling UDP
> + * fragmentation in SW or in HW. When use UFO, mbuf->tso_segsz is used
> + * to store the MSS of UDP fragments.
> + */
> +#define PKT_TX_UDP_SEG (1ULL << 42)
This patch added a new mbuf flag, Olivier, do you have objections?
--yliu
next prev parent reply other threads:[~2017-12-27 14:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 6:56 Jiayu Hu
2017-11-21 7:12 ` Stephen Hemminger
2017-11-21 7:41 ` Hu, Jiayu
2017-11-21 14:33 ` Neil Horman
2017-12-05 14:57 ` Maxime Coquelin
2017-12-06 8:36 ` Maxime Coquelin
2017-12-07 13:14 ` Hu, Jiayu
2017-12-25 1:48 ` Yao, Lei A
2017-12-27 14:34 ` Yuanhan Liu [this message]
2018-01-08 14:27 ` Yuanhan Liu
2018-01-16 11:20 ` Thomas Monjalon
2018-01-16 12:21 ` Olivier Matz
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=20171227143454.GH8818@yliu-mob \
--to=yliu@fridaylinux.org \
--cc=dev@dpdk.org \
--cc=jianfeng.tan@intel.com \
--cc=jiayu.hu@intel.com \
--cc=olivier.matz@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).