From: Andrea Arcangeli <andrea@suse.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
bcrl@redhat.com
Subject: Re: [patch] softirq performance fixes, cleanups, 2.4.10.
Date: Fri, 28 Sep 2001 18:58:00 +0200 [thread overview]
Message-ID: <20010928185800.M24922@athlon.random> (raw)
In-Reply-To: <20010928183244.K24922@athlon.random> <Pine.LNX.4.33.0109281835370.8840-100000@localhost.localdomain>
In-Reply-To: <Pine.LNX.4.33.0109281835370.8840-100000@localhost.localdomain>; from mingo@elte.hu on Fri, Sep 28, 2001 at 06:46:16PM +0200
On Fri, Sep 28, 2001 at 06:46:16PM +0200, Ingo Molnar wrote:
>
> On Fri, 28 Sep 2001, Andrea Arcangeli wrote:
>
> > he's allowing to repeat the loop more than once to hide it, [...]
>
> it's not done to 'hide' it in any way. I removed the mask method because
> it's redundant under the new scheme.
What you are missing is a property provided by the old method.
We have the NET_RX_SOFTIRQ that floods very heavily, so far so good.
Then we have HI_SOFTIRQ, incidentally HI_SOFTIRQ from irq wants to be
executed with very low latency, with your patch it _can_ be postpone to
ksoftirqd processing just because there's the NET_RX_SOFTIRQ cpu hog in
background. With the old method it was guaranteed that the HI_SOFTIRQ
was executed with very low latency within the irq, no matter of the
NET_RX_SOFTIRQ flood.
So there _is_ a difference, and the multiple-loop will tend to "hide"
the difference.
Andrea
next prev parent reply other threads:[~2001-09-28 16:57 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-26 16:44 [patch] softirq performance fixes, cleanups, 2.4.10 Ingo Molnar
2001-09-26 17:48 ` Mike Kravetz
2001-09-26 18:48 ` Ingo Molnar
2001-09-26 18:55 ` Russell King
2001-09-26 19:14 ` Ingo Molnar
2001-09-27 23:31 ` Andrea Arcangeli
2001-09-28 3:20 ` Andrea Arcangeli
2001-09-28 7:34 ` Ingo Molnar
2001-09-28 15:17 ` Andrea Arcangeli
2001-09-28 7:18 ` [patch] softirq-2.4.10-B2 Ingo Molnar
2001-09-28 15:58 ` Andrea Arcangeli
2001-09-28 18:36 ` Simon Kirby
2001-09-28 18:47 ` Ingo Molnar
2001-09-28 19:31 ` kuznet
2001-09-28 16:18 ` [patch] softirq performance fixes, cleanups, 2.4.10 kuznet
2001-09-28 16:31 ` Ingo Molnar
2001-09-28 17:04 ` kuznet
2001-09-28 17:21 ` Rik van Riel
2001-09-28 17:31 ` Andrea Arcangeli
2001-09-28 17:41 ` kuznet
2001-09-28 17:46 ` Ingo Molnar
2001-09-28 18:39 ` Josh MacDonald
2001-09-28 17:31 ` Ingo Molnar
2001-09-28 17:56 ` kuznet
2001-09-28 18:28 ` Ingo Molnar
2001-09-28 19:23 ` kuznet
2001-09-28 19:48 ` Ingo Molnar
2001-09-29 16:35 ` kuznet
2001-09-30 9:37 ` Kai Henningsen
2001-09-30 9:01 ` Ingo Molnar
2001-09-28 19:39 ` kuznet
2001-09-28 20:03 ` Ingo Molnar
2001-09-28 18:51 ` Benjamin LaHaise
2001-09-28 16:32 ` Andrea Arcangeli
2001-09-28 16:46 ` Ingo Molnar
2001-09-28 16:58 ` Andrea Arcangeli [this message]
2001-09-28 16:35 ` [patch] softirq-2.4.10-B3 Ingo Molnar
2001-09-29 0:40 ` J . A . Magallon
2001-09-29 11:03 ` [patch] softirq performance fixes, cleanups, 2.4.10 Rusty Russell
-- strict thread matches above, loose matches on Subject: below --
2001-09-27 23:29 Oleg Nesterov
2001-09-28 0:03 ` Andrea Arcangeli
2001-09-28 6:57 ` Ingo Molnar
2001-09-28 2:50 Oleg Nesterov
2001-09-28 7:56 ` Ingo Molnar
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=20010928185800.M24922@athlon.random \
--to=andrea@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bcrl@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@transmeta.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