From: Eric Dumazet <eric.dumazet@gmail.com>
To: Micha Nelissen <micha@neli.hopto.org>
Cc: Michael Durket <durket@highwire.stanford.edu>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: Question about tg3 and bnx2 driver suppliers
Date: Sun, 20 Feb 2011 20:17:00 +0100 [thread overview]
Message-ID: <1298229420.8559.59.camel@edumazet-laptop> (raw)
In-Reply-To: <4D615B2D.5080804@neli.hopto.org>
Le dimanche 20 février 2011 à 19:19 +0100, Micha Nelissen a écrit :
> Eric Dumazet wrote:
> > One possible cause of packet drops is when softirqs are disabled for too
> > long periods, even if NIC has a big RX ring (check ethtool -g eth0)
>
> Why aren't the softirqs converted to workqueues? Wouldn't that cut
> dependencies to other softirq users and improve latency?
>
Because it was done like that in the old days.
Its a bit less important these days, now typical machines have 8+ cpus.
Each device interrupt can be handled by its own cpu :)
next prev parent reply other threads:[~2011-02-20 19:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 13:24 Question about tg3 and bnx2 driver suppliers Michael Durket
2011-02-17 14:16 ` Ben Hutchings
2011-02-17 14:17 ` Eric Dumazet
2011-02-20 18:19 ` Micha Nelissen
2011-02-20 19:17 ` Eric Dumazet [this message]
2011-02-20 20:41 ` Stephen Hemminger
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=1298229420.8559.59.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=durket@highwire.stanford.edu \
--cc=micha@neli.hopto.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox