From: Stephen Hemminger <shemminger@vyatta.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Micha Nelissen <micha@neli.hopto.org>,
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 12:41:15 -0800 [thread overview]
Message-ID: <20110220124115.730eca80@nehalam> (raw)
In-Reply-To: <1298229420.8559.59.camel@edumazet-laptop>
On Sun, 20 Feb 2011 20:17:00 +0100
Eric Dumazet <eric.dumazet@gmail.com> wrote:
> 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 :)
The latency to schedule a work queue is still much higher
than the latency to do a softirq. Last time I played around with it,
things like loopback performance dropped 10% if using work queue.
prev parent reply other threads:[~2011-02-20 20:41 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
2011-02-20 20:41 ` Stephen Hemminger [this message]
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=20110220124115.730eca80@nehalam \
--to=shemminger@vyatta.com \
--cc=durket@highwire.stanford.edu \
--cc=eric.dumazet@gmail.com \
--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