DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Tan, Jianfeng" <jianfeng.tan@intel.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Maxime Coquelin <maxime.coquelin@redhat.com>,
	"Liu, Yuanhan" <yuanhan.liu@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] vhost user MTU and promisc mode
Date: Wed, 8 Feb 2017 09:34:56 +0000	[thread overview]
Message-ID: <ED26CBA2FAD1BF48A8719AEF02201E365112DD59@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <20170207183203-mutt-send-email-mst@kernel.org>



> -----Original Message-----
> From: Michael S. Tsirkin [mailto:mst@redhat.com]
> Sent: Wednesday, February 8, 2017 12:33 AM
> To: Tan, Jianfeng
> Cc: Maxime Coquelin; Liu, Yuanhan; dev@dpdk.org
> Subject: Re: vhost user MTU and promisc mode
> 
> On Tue, Feb 07, 2017 at 04:27:16PM +0000, Tan, Jianfeng wrote:
> >
> >
> > > -----Original Message-----
> > > From: Maxime Coquelin [mailto:maxime.coquelin@redhat.com]
> > > Sent: Monday, February 6, 2017 6:20 PM
> > > To: Tan, Jianfeng
> > > Cc: mst@redhat.com; Liu, Yuanhan; dev@dpdk.org
> > > Subject: Re: vhost user MTU and promisc mode
> > >
> > > Hi Jianfeng,
> > >
> > > On 02/06/2017 07:39 AM, Tan, Jianfeng wrote:
> > > > Hi Maxime,
> > > >
> > > >
> > > >
> > > > Have seen that you submit a feature in QEMU, commit c5f048d8fb69
> > > > ("vhost-user: Add MTU protocol feature and op").
> > > >
> > > >
> > > >
> > > > Appreciate your insights on:
> > > >
> > > > (1) Do you have plan to enable it in DPDK vhost user?
> > > Yes, I plan to propose this for v17.05 release.
> > > For vhost-user backend, the op is to notify the backend with the MTU
> > > value set in QEMU, so that it can ensure packets sent won't be bigger.
> >
> > Great to know that.
> >
> > >
> > > >
> > > > (2) How about another similar feature, promisc mode enable/disable?
> > > This is ont something we have considered yet.
> > > Are you willing to work on it?
> >
> > Yes, we are considering it. But it should be firstly upsteamed into QEMU.
> >
> > Thanks,
> > Jianfeng
> 
> You also need to copy virtio tc list if you will suggest
> interface changes. TC is responsible for documenting it.

Thank you Michael for reminding! We will do that in a separated thread.

Thanks,
Jianfeng

> 
> > >
> > > Thanks,
> > > Maxime
> > >
> > > >
> > > >
> > > > Thanks,
> > > >
> > > > Jianfeng
> > > >

      reply	other threads:[~2017-02-08  9:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-06  6:39 Tan, Jianfeng
2017-02-06 10:19 ` Maxime Coquelin
2017-02-07 16:27   ` Tan, Jianfeng
2017-02-07 16:32     ` Michael S. Tsirkin
2017-02-08  9:34       ` Tan, Jianfeng [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=ED26CBA2FAD1BF48A8719AEF02201E365112DD59@SHSMSX103.ccr.corp.intel.com \
    --to=jianfeng.tan@intel.com \
    --cc=dev@dpdk.org \
    --cc=maxime.coquelin@redhat.com \
    --cc=mst@redhat.com \
    --cc=yuanhan.liu@intel.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).