From: "Hu, Jiayu" <jiayu.hu@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"yliu@fridaylinux.org" <yliu@fridaylinux.org>,
"Tan, Jianfeng" <jianfeng.tan@intel.com>
Subject: Re: [dpdk-dev] [PATCH] vhost: support UDP Fragmentation Offload
Date: Tue, 21 Nov 2017 07:41:00 +0000 [thread overview]
Message-ID: <ED946F0BEFE0A141B63BABBD629A2A9B38811A05@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <20171120231236.399555e6@xeon-e3>
Hi Stephen,
> -----Original Message-----
> From: Stephen Hemminger [mailto:stephen@networkplumber.org]
> Sent: Tuesday, November 21, 2017 3:13 PM
> To: Hu, Jiayu <jiayu.hu@intel.com>
> Cc: dev@dpdk.org; yliu@fridaylinux.org; Tan, Jianfeng
> <jianfeng.tan@intel.com>
> Subject: Re: [dpdk-dev] [PATCH] vhost: support UDP Fragmentation Offload
>
> On Tue, 21 Nov 2017 14:56:52 +0800
> Jiayu Hu <jiayu.hu@intel.com> 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>
>
> This may no longer be a desirable feature to implement.
> UFO was just deprecated and removed from Linux.
> It had no useful benefit.
The main reason of supporting UFO is to make the backend live migration from
vhost-net to vhost-user possible. Host and guest UFO are default features for virtio-net,
and vhost-net supports both. But vhosy-user doesn't support them. If we want to
migrate from vhost-net to vhost-user, this features gap would cause live migration fail.
Thanks,
Jiayu
next prev parent reply other threads:[~2017-11-21 7:42 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 [this message]
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
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=ED946F0BEFE0A141B63BABBD629A2A9B38811A05@shsmsx102.ccr.corp.intel.com \
--to=jiayu.hu@intel.com \
--cc=dev@dpdk.org \
--cc=jianfeng.tan@intel.com \
--cc=stephen@networkplumber.org \
--cc=yliu@fridaylinux.org \
/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).