netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@gmail.com>
To: jamal <hadi@cyberus.ca>
Cc: Changli Gao <xiaosuo@gmail.com>, netdev@vger.kernel.org
Subject: Re: [PATCH 3/3] ifb: move tq from ifb_private
Date: Sat, 4 Dec 2010 17:56:09 +0100	[thread overview]
Message-ID: <20101204165609.GB1981@del.dom.local> (raw)
In-Reply-To: <1291478881.2159.70.camel@mojatatu>

On Sat, Dec 04, 2010 at 11:08:01AM -0500, jamal wrote:
> On Sat, 2010-12-04 at 16:40 +0100, Jarek Poplawski wrote:
> 
> > Hmm... But we didn't care until now... ;-) 
> 
> Well, if Changli didnt post - there would be no discussion ;->
> The message was lost in the translation somewhere; events such as
> patches sometimes serve as good reminders.
> 
> > Btw. is it really very
> > probable (and worth bothering) that this current error of NULL dev
> > get fixed before we purge this tq queue with deferral one by one?
> 
> Indeed - this is working against something buggy. But it has happened
> often in the past. And the likelihood of there being a few bad ones
> in the train of packets when this occurs is high. But there are many
> packets there that wont suffer this sympton - so the only fair scheme is
> to check all. Note: a BUG() seems unreasonable and the deferring  serves
> as a throttling scheme.
> What do you have in mind?

I'm simply not convinced this kind of (fast) throttling can properly
fix any of the problems (what about other flows in the queue), while
Changli's patch makes this tasklet simpler and a bit faster.

Cheers,
Jarek P.

  reply	other threads:[~2010-12-04 16:56 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-04  5:55 [PATCH 1/3] ifb: remove the useless debug stats Changli Gao
2010-12-04  5:55 ` [PATCH 2/3] ifb: remove unused macro TX_TIMEOUT Changli Gao
2010-12-04 14:13   ` jamal
2010-12-04  5:55 ` [PATCH 3/3] ifb: move tq from ifb_private Changli Gao
2010-12-04 13:15   ` Jarek Poplawski
2010-12-04 13:29     ` Changli Gao
2010-12-04 14:28     ` jamal
2010-12-04 14:45       ` Changli Gao
2010-12-04 14:55         ` jamal
2010-12-04 15:01           ` Changli Gao
2010-12-04 15:09             ` jamal
2010-12-04 14:48       ` jamal
2010-12-04 15:40         ` Jarek Poplawski
2010-12-04 16:08           ` jamal
2010-12-04 16:56             ` Jarek Poplawski [this message]
2010-12-05  0:22               ` Changli Gao
2010-12-05  1:13                 ` Changli Gao
2010-12-05 14:30                   ` jamal
2010-12-05 14:40                     ` Changli Gao
2010-12-05 15:13                       ` Eric Dumazet
2010-12-05 15:16                         ` Changli Gao
2010-12-05 15:13                       ` jamal
2010-12-05 15:22                         ` Changli Gao
2010-12-05 15:31                           ` jamal
2010-12-05 14:27                 ` jamal
2010-12-05 19:09                   ` Jarek Poplawski
2010-12-04 14:18   ` jamal
2010-12-04 14:20     ` Changli Gao
2010-12-04 14:42     ` jamal
2010-12-04 14:50       ` Changli Gao
2010-12-04 14:59         ` jamal
2010-12-04 15:07           ` Changli Gao
2010-12-04 15:11             ` jamal
2010-12-04 14:12 ` [PATCH 1/3] ifb: remove the useless debug stats jamal

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=20101204165609.GB1981@del.dom.local \
    --to=jarkao2@gmail.com \
    --cc=hadi@cyberus.ca \
    --cc=netdev@vger.kernel.org \
    --cc=xiaosuo@gmail.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).