From: Robert Olsson <Robert.Olsson@data.slu.se>
To: Steffen Persvold <sp@scali.com>
Cc: Robert Olsson <Robert.Olsson@data.slu.se>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
"David S. Miller" <davem@redhat.com>,
Jeff Garzik <jgarzik@pobox.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: NAPI and tg3
Date: Tue, 7 Jan 2003 23:21:08 +0100 [thread overview]
Message-ID: <15899.21204.884559.523678@robur.slu.se> (raw)
Steffen Persvold writes:
> True, but it doesn't say that if you have two applications loaded on
> a SMP box, one which is for example constantly receiving and sending data
> from/to the network and doing computations on the data (100 % CPU) while
> some other app is only doing computations (also 100 % CPU), the ksoftirqd
> which should receive packets and refill the TX and RX rings will be put
> last in the queue because of its low nice level (19), thus the network
> dependent application has very much lower performance than what could be
> achieved with a nice level of 0 or even running the interrupt based
> mechanism. A nice level of 0 on ksoftirqd is still a heck of a lot better
> than interrupt context isn't it ?
Yes my scripts test/production has even been setting -19 to ksoftirq just
for that reason so I almost forgot this issue so I'm happy you brought
this up. But dev->poll is not the only user of ksoftirq but for heavy
networking it's gets pretty dominant. So we add something to NAPI_HOWTO
and pass the question about ksoftirq default priority to others.
>From a GIGE router in production.
USER PID %CPU %MEM SIZE RSS TTY STAT START TIME COMMAND
root 3 0.2 0.0 0 0 ? RWN Aug 15 602:00 (ksoftirqd_CPU0)
root 232 0.0 7.9 41400 40884 ? S Aug 15 74:12 gated
Cheers.
--ro
next reply other threads:[~2003-01-07 22:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-07 22:21 Robert Olsson [this message]
2003-01-08 0:07 ` Steffen Persvold
2003-01-09 17:21 ` Robert Olsson
2003-01-10 9:00 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2003-01-04 15:23 Steffen Persvold
2003-01-06 15:00 ` Steffen Persvold
2003-01-06 16:36 ` Alan Cox
2003-01-06 16:12 ` Steffen Persvold
2003-01-06 17:58 ` Alan Cox
2003-01-07 15:24 ` Steffen Persvold
2003-01-07 18:51 ` Robert Olsson
2003-01-07 20:54 ` Steffen Persvold
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=15899.21204.884559.523678@robur.slu.se \
--to=robert.olsson@data.slu.se \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sp@scali.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
all inboxes | Powered by JetHome®