From: Andrea Arcangeli <andrea@suse.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@transmeta.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
"David S. Miller" <davem@redhat.com>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
arjanv@redhat.com
Subject: Re: [patch] softirq-2.4.5-A1
Date: Sun, 27 May 2001 22:05:36 +0200 [thread overview]
Message-ID: <20010527220536.B731@athlon.random> (raw)
In-Reply-To: <20010527191249.I676@athlon.random> <Pine.LNX.4.33.0105272106340.5852-100000@localhost.localdomain>
In-Reply-To: <Pine.LNX.4.33.0105272106340.5852-100000@localhost.localdomain>; from mingo@elte.hu on Sun, May 27, 2001 at 09:08:51PM +0200
On Sun, May 27, 2001 at 09:08:51PM +0200, Ingo Molnar wrote:
> i took at look at your ksoftirq stuff yesterday, and i think it's
> completely unnecessery and adds serious overhead to softirq handling. The
> whole point of softirqs is to have maximum scalability and no
> serialization. Why did you add ksoftirqd, would you mind explaining it?
The only case ksoftirqd runs is when the stock kernel does the wrong
thing and potentially delays the softirq of 1/HZ. Nothing else.
When current kernel does the right thing ksoftirq cannot generate any
scalability problem and furthmore ksoftirqd is a per-cpu thing so if you
face a scalability problem with it that simply means you need to fix the
scheduler because then it means you would face a scalability issue as
well every time a tux thread calls schedule().
90% of the time ksoftirqd will never run, when it runs it means you want
to pay for a scheduler run to get it running. The price of the scheduler
is just the price for the logic that balance the softirq load in a fair
manner and without buggy latencies.
Andrea
next prev parent reply other threads:[~2001-05-27 20:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-26 17:59 [patch] severe softirq handling performance bug, fix, 2.4.5 Ingo Molnar
2001-05-26 19:33 ` [patch] softirq-2.4.5-A1 Ingo Molnar
2001-05-27 17:12 ` Andrea Arcangeli
2001-05-27 19:08 ` Ingo Molnar
2001-05-27 20:05 ` Andrea Arcangeli [this message]
2001-05-28 1:17 ` Horst von Brand
2001-05-26 23:55 ` [patch] severe softirq handling performance bug, fix, 2.4.5 David S. Miller
2001-05-27 3:28 ` Albert D. Cahalan
2001-05-27 17:18 ` Andrea Arcangeli
2001-05-27 19:00 ` [patch] softirq-2.4.5-B0 Ingo Molnar
2001-05-27 19:15 ` David S. Miller
2001-05-27 19:19 ` Ingo Molnar
2001-05-27 17:07 ` [patch] severe softirq handling performance bug, fix, 2.4.5 Andrea Arcangeli
2001-05-27 17:17 ` David S. Miller
2001-05-27 17:56 ` Andrea Arcangeli
2001-05-27 19:05 ` Ingo Molnar
2001-05-27 19:55 ` Andrea Arcangeli
2001-05-27 21:00 ` Ingo Molnar
2001-05-28 19:26 ` kuznet
2001-05-27 19:09 ` David S. Miller
2001-05-27 20:24 ` Andrea Arcangeli
2001-06-10 10:40 ` Rusty Russell
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=20010527220536.B731@athlon.random \
--to=andrea@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjanv@redhat.com \
--cc=davem@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