DPDK patches and discussions
 help / color / mirror / Atom feed
From: Yuanhan Liu <yliu@fridaylinux.org>
To: Tiwei Bie <tiwei.bie@intel.com>
Cc: "Fischetti, Antonio" <antonio.fischetti@intel.com>,
	zhihong.wang@intel.com, stable@dpdk.org, dev@dpdk.org
Subject: Re: [dpdk-dev] Your next patch "net/virtio: fix an incorrect behavior..."
Date: Wed, 6 Dec 2017 15:39:37 +0800	[thread overview]
Message-ID: <20171206073937.GA17112@yliu-dev> (raw)
In-Reply-To: <20171206071148.43horopz23zr7cmu@debian-xvivbkq>

Thanks for the remind! I have reverted it.

	--yliu

On Wed, Dec 06, 2017 at 03:11:48PM +0800, Tiwei Bie wrote:
> Hi Yuanhan,
> 
> Thanks for Antonio's reminder!
> 
> Below patch may break vector Rx in some cases [1].
> 
> http://dpdk.org/browse/dpdk-stable/commit/drivers/net/virtio?h=17.08&id=f4e455b776f61ec7fbdfb5dce6ba34ad9016689b
> 
> And I'm working on a fix for it. But as the deadline of 17.08.1
> is approaching, we don't have enough time to get the fix reviewed
> and tested by the community. I'm not sure, maybe we should remove
> it from the stable branch for 17.08.1 for now?
> 
> [1] http://dpdk.org/ml/archives/dev/2017-December/082983.html
> 
> Best regards,
> Tiwei Bie
> 
> On Tue, Dec 05, 2017 at 09:14:39PM +0800, Fischetti, Antonio wrote:
> > Thanks Tiwei,
> > one more thing. I saw they are going to backport some patches into 17.08.1
> > 
> > http://dev.dpdk.narkive.com/pX0IIwPl/dpdk-dev-17-08-1-patches-review-and-test
> > 
> > is your next fix related to the one reported as "net/virtio: flush Rx queues on start"?
> > 
> > If that's the case, should we flag this to Yuanhan Liu, just to be aware there's some work in progress?
> > 
> > 
> > Antonio
> > 

           reply	other threads:[~2017-12-06  7:40 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20171206071148.43horopz23zr7cmu@debian-xvivbkq>]

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=20171206073937.GA17112@yliu-dev \
    --to=yliu@fridaylinux.org \
    --cc=antonio.fischetti@intel.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    --cc=tiwei.bie@intel.com \
    --cc=zhihong.wang@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).