From: David Miller <davem@davemloft.net>
To: axboe@suse.de
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: softirq considered harmful
Date: Mon, 14 Aug 2006 01:44:48 -0700 (PDT) [thread overview]
Message-ID: <20060814.014448.30183193.davem@davemloft.net> (raw)
In-Reply-To: <20060814073724.GJ4231@suse.de>
From: Jens Axboe <axboe@suse.de>
Date: Mon, 14 Aug 2006 09:37:25 +0200
> Hopefully you often end up doing > 1 request for a busy IO sub system,
> otherwise the softirq stuff is pointless. But it's still pretty bad for
> single requests.
Note that the per-cpu softirq completion of I/O events means
that the queue can be processed lockless.
I'm not saying this justifies softirq I/O completion, I'm just
mentioning it as one benefit of the scheme. This is also why
networking uses softirqs for the core irq events instead of
tasklets.
It appears the scsi code uses hw IRQ locking for all of it's
locking so that should be fine.
However there might be some scsi exception handling dependencies
on the completions being run in software irq context, but this is
just a guess.
iSCSI would need to be checked out too.
next prev parent reply other threads:[~2006-08-14 8:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 11:06 softirq considered harmful Jens Axboe
2006-08-10 11:41 ` David Miller
2006-08-10 12:26 ` Jens Axboe
2006-08-12 23:28 ` Andrew Morton
2006-08-13 0:43 ` David Miller
2006-08-13 0:45 ` Andrew Morton
2006-08-13 1:09 ` David Miller
2006-08-13 1:22 ` Andrew Morton
2006-08-14 7:37 ` Jens Axboe
2006-08-14 8:44 ` David Miller [this message]
2006-08-14 8:51 ` Jens Axboe
2006-08-14 7:34 ` Jens Axboe
2006-08-13 14:31 ` Jens Axboe
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=20060814.014448.30183193.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--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