From: Robert Olsson <Robert.Olsson@data.slu.se>
To: "David S. Miller" <davem@redhat.com>
Cc: Steffen Persvold <sp@scali.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Robert Olsson <Robert.Olsson@data.slu.se>,
Jeff Garzik <jgarzik@pobox.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: NAPI and tg3
Date: Thu, 9 Jan 2003 18:21:00 +0100 [thread overview]
Message-ID: <15901.44924.430586.886@robur.slu.se> (raw)
In-Reply-To: <Pine.LNX.4.44.0301080059060.1128-100000@sp-laptop.isdn.scali.no>
Before it's get forgotten...
Cheers.
--ro
--- NAPI_HOWTO.txt.orig 2002-12-24 06:20:31.000000000 +0100
+++ NAPI_HOWTO.txt 2003-01-09 13:25:30.000000000 +0100
@@ -721,6 +721,23 @@
+
+APPENDIX 3: Scheduling issues.
+==============================
+As seen NAPI moves processing to softirq level. Linux uses the ksoftirqd as the
+general solution to schedule softirq's to run before next interrupt and by putting
+them under scheduler control. Also this prevents consecutive softirq's from
+monopolize the CPU. This also have the effect that the priority of ksoftirq needs
+to be considered when running very CPU-intensive applications and networking to
+get the proper balance of softirq/user balance. Increasing ksoftirq priority to 0
+(eventually more) is reported cure problems with low network performance at high
+CPU load.
+
+Most used processes in a GIGE router:
+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
+
--------------------------------------------------------------------
relevant sites:
next prev parent reply other threads:[~2003-01-09 17:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-07 22:21 NAPI and tg3 Robert Olsson
2003-01-08 0:07 ` Steffen Persvold
2003-01-09 17:21 ` Robert Olsson [this message]
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=15901.44924.430586.886@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