All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>, huawei.xie@intel.com
Cc: dev@dpdk.org
Subject: Re: [PATCH] virtio: fix rx ring descriptor starvation
Date: Wed, 25 Nov 2015 09:50:01 +0800	[thread overview]
Message-ID: <20151125015001.GL2325@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <1980495.CSRm2jjoLQ@xps13>

On Tue, Nov 24, 2015 at 10:20:22PM +0100, Thomas Monjalon wrote:
> Any review, please?

Huawei, would you review it? Sorry that I've not read too much
code about virtio PMD driver yet.

	--yliu


> 2015-11-13 09:30, Tom Kiely:
> > If all rx descriptors are processed while transient
> > mbuf exhaustion is present, the rx ring ends up with
> > no available descriptors. Thus no packets are received
> > on that ring. Since descriptor refill is performed post
> > rx descriptor processing, in this case no refill is
> > ever subsequently performed resulting in permanent rx
> > traffic drop.
> > 
> > Signed-off-by: Tom Kiely <tkiely@brocade.com>

  reply	other threads:[~2015-11-25  1:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-13  9:30 [PATCH] virtio: fix rx ring descriptor starvation Tom Kiely
2015-11-24 21:20 ` Thomas Monjalon
2015-11-25  1:50   ` Yuanhan Liu [this message]
2015-11-25  2:51     ` Xie, Huawei
2015-11-25 17:32 ` Xie, Huawei
2015-12-17  4:47   ` Xie, Huawei
2015-12-17  9:22     ` Tom Kiely
2015-12-17 11:18   ` Tom Kiely
2016-01-05  7:13     ` Xie, Huawei
2016-02-10 15:07       ` Bruce Richardson
2016-02-18 14:03       ` Kyle Larose
2016-02-22 16:23         ` Tom Kiely
2016-02-23  8:26           ` Xie, Huawei
2016-03-04  6:16           ` Xie, Huawei
2016-03-04  8:11             ` Tom Kiely
2016-03-04 13:25               ` Kyle Larose
2016-03-09 21:37                 ` Bruce Richardson
2016-03-10 14:46                   ` Kyle Larose
  -- strict thread matches above, loose matches on Subject: below --
2016-02-26 18:58 Kyle Larose

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=20151125015001.GL2325@yliu-dev.sh.intel.com \
    --to=yuanhan.liu@linux.intel.com \
    --cc=dev@dpdk.org \
    --cc=huawei.xie@intel.com \
    --cc=thomas.monjalon@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 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.