From: Scott Feldman <scofeldm@cisco.com>
To: Simon Horman <horms@verge.net.au>
Cc: <davem@davemloft.net>, <netdev@vger.kernel.org>
Subject: Re: [net-next PATCH 2/6] enic: Bug fix: try harder to fill Rx ring on skb allocation failures
Date: Sat, 19 Dec 2009 17:29:43 -0800 [thread overview]
Message-ID: <C752BE07.1B019%scofeldm@cisco.com> (raw)
In-Reply-To: <20091220011500.GA12578@verge.net.au>
On 12/19/09 5:15 PM, "Simon Horman" <horms@verge.net.au> wrote:
> On Sat, Dec 19, 2009 at 12:39:03PM -0800, Scott Feldman wrote:
>>>> + rq_work_done = rq_work_to_do;
>>>
>>> Is it intentional for rq_work_done = rq_work_to_do to become the
>>> return value?
>>
>> That was intentional. If the replacement skb allocation fails, we're
>> returning like we did a full budget's worth of work so we stay scheduled and
>> hopefully the next polling pass we'll get the allocations. Before this fix,
>> there is a corner case which isn't covered: if hw has used all descs and
>> gens an intr and we get into polling and the replacement alloc fails, then
>> Rx is hung. Hw is desc starved and we're not going to get any more intrs:
>> game over.
>
> Ok, understood. Though doesn't this fix just narrow the scope for that
> failure? It seems that it could still occur in a pathological case.
Oh! The intention was to fix it absolutely. Please expand on the
pathological case your thinking about. We need this 100% solved, but now
you've got me worried... ;)
-scott
next prev parent reply other threads:[~2009-12-20 1:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-19 2:09 [net-next PATCH 0/6] enic: updates to version 1.1.0.241 Scott Feldman
2009-12-19 2:09 ` [net-next PATCH 1/6] enic: Bug fix: use safe queue shutdown in dev->stop Scott Feldman
2009-12-19 15:34 ` Ben Hutchings
2009-12-19 20:44 ` Scott Feldman
2009-12-19 2:09 ` [net-next PATCH 2/6] enic: Bug fix: try harder to fill Rx ring on skb allocation failures Scott Feldman
2009-12-19 10:41 ` Simon Horman
2009-12-19 20:39 ` Scott Feldman
2009-12-20 1:15 ` Simon Horman
2009-12-20 1:29 ` Scott Feldman [this message]
2009-12-20 6:14 ` Simon Horman
2009-12-20 1:51 ` Scott Feldman
2009-12-20 6:54 ` Simon Horman
2009-12-19 2:09 ` [net-next PATCH 3/6] enic: minimize pkt filter updates to firmware Scott Feldman
2009-12-19 2:09 ` [net-next PATCH 4/6] enic: Bug fix: align desc ring sizes to 32 descs Scott Feldman
2009-12-19 2:10 ` [net-next PATCH 5/6] enic: feature add: add ethtool -c/C support Scott Feldman
2009-12-19 10:10 ` Simon Horman
2009-12-19 19:33 ` Scott Feldman
2009-12-20 1:15 ` Simon Horman
2009-12-19 2:10 ` [net-next PATCH 6/6] enic: whitespace cleanup; #define cleanup; more verbose err msg Scott Feldman
-- strict thread matches above, loose matches on Subject: below --
2009-12-22 2:21 [net-next PATCH 0/6] enic: updates to version 1.1.0.241a Scott Feldman
2009-12-22 2:21 ` [net-next PATCH 2/6] enic: Bug fix: try harder to fill Rx ring on skb allocation failures Scott Feldman
2009-12-23 23:27 [net-next PATCH 0/6] enic: updates to version 1.1.0.241a Scott Feldman
2009-12-23 23:27 ` [net-next PATCH 2/6] enic: Bug fix: try harder to fill Rx ring on skb allocation failures Scott Feldman
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=C752BE07.1B019%scofeldm@cisco.com \
--to=scofeldm@cisco.com \
--cc=davem@davemloft.net \
--cc=horms@verge.net.au \
--cc=netdev@vger.kernel.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.