All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olivier Matz <olivier.matz@6wind.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Jiayu Hu <jiayu.hu@intel.com>,
	dev@dpdk.org, Yuanhan Liu <yliu@fridaylinux.org>,
	jianfeng.tan@intel.com
Subject: Re: [PATCH] vhost: support UDP Fragmentation Offload
Date: Tue, 16 Jan 2018 13:21:33 +0100	[thread overview]
Message-ID: <20180116122133.5764kdxh5tf754tj@platinum> (raw)
In-Reply-To: <4548500.UFps53m4kA@xps>

On Tue, Jan 16, 2018 at 12:20:48PM +0100, Thomas Monjalon wrote:
> 08/01/2018 15:27, Yuanhan Liu:
> > 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>
> > 
> > Applied to dpdk-next-virtio.
> 
> Olivier Matz, mbuf maintainer, was not Cc'ed in this patch.
> Olivier, can you confirm this new mbuf flag is OK?

Yuanhan CC'ed me, but I was quite busy at that time.

Even if it's to late:
Acked-by: Olivier Matz <olivier.matz@6wind.com>

      reply	other threads:[~2018-01-16 12:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-21  6:56 [PATCH] vhost: support UDP Fragmentation Offload 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
2018-01-08 14:27 ` Yuanhan Liu
2018-01-16 11:20   ` Thomas Monjalon
2018-01-16 12:21     ` Olivier Matz [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=20180116122133.5764kdxh5tf754tj@platinum \
    --to=olivier.matz@6wind.com \
    --cc=dev@dpdk.org \
    --cc=jianfeng.tan@intel.com \
    --cc=jiayu.hu@intel.com \
    --cc=thomas@monjalon.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.