From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Robert Hancock <hancockr@shaw.ca>
Cc: danial_thom@yahoo.com, "\"Pádraig\"Brady" <P@draigBrady.com>,
linux-kernel@vger.kernel.org
Subject: Re: Dropping Packets in 2.6.17
Date: Fri, 23 Jun 2006 01:31:28 -0600 [thread overview]
Message-ID: <20060623013128.A32391@openss7.org> (raw)
In-Reply-To: <449B4038.3040101@shaw.ca>; from hancockr@shaw.ca on Thu, Jun 22, 2006 at 07:13:28PM -0600
Robert,
On Thu, 22 Jun 2006, Robert Hancock wrote:
>
> If you want to give more priority to processing network packets at the
> expense of user processes then you likely need to increase the priority
> of the ksoftirqd thread(s). These compete for CPU time like any other
> processes.
>
I don't think that's a fair statement:
- "any other process" does not execute when returning from an interrupt
as do softirq threads
- "any other process" does not execute upon local_bh_enable().
- "any other process" is blockable (which at softirq is a big BUG()).
Under moderate to heavy load, throttling (or disabling) hard interrupts
effectively reduces the priority of ksoftirqd threads (they have less
opportunity to run because interrupts are returning less often).
next prev parent reply other threads:[~2006-06-23 7:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.zPWsMAz4l0d9j5Voaw6Pdkcf//M@ifi.uio.no>
[not found] ` <fa.Ze3oSnDYEMz3/ITqeLQ2m0GF5wk@ifi.uio.no>
2006-06-23 1:13 ` Dropping Packets in 2.6.17 Robert Hancock
2006-06-23 7:31 ` Brian F. G. Bidulock [this message]
2006-06-23 19:48 ` Danial Thom
2006-06-22 11:31 Danial Thom
2006-06-22 11:55 ` Arjan van de Ven
2006-06-22 12:47 ` Danial Thom
2006-06-22 13:27 ` Pádraig Brady
2006-06-22 14:01 ` Miquel van Smoorenburg
2006-06-22 14:15 ` Pádraig Brady
2006-06-22 15:03 ` Danial Thom
2006-06-22 15:26 ` Pádraig Brady
2006-06-22 17:10 ` Danial Thom
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=20060623013128.A32391@openss7.org \
--to=bidulock@openss7.org \
--cc=P@draigBrady.com \
--cc=danial_thom@yahoo.com \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@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