From: David Miller <davem@davemloft.net>
To: linux-kernel@vger.kernel.org
Cc: netdev@vger.kernel.org, jens.axboe@oracle.com,
steffen.klassert@secunet.com
Subject: [PATCH 0/2]: Remote softirq invocation infrastructure.
Date: Fri, 19 Sep 2008 23:48:24 -0700 (PDT) [thread overview]
Message-ID: <20080919.234824.223177211.davem@davemloft.net> (raw)
Jens Axboe has written some hacks for the block layer that allow
queueing softirq work to remote cpus. In the context of the block
layer he used this facility to trigger the softirq block I/O
completion on the same cpu where the I/O was submitted.
I want to make use of a similar facility for the networking, so we
should make this thing generic.
It depends upon the generic SMP call function infrastructure, which
Jens wrote specifically to do these remote softirq hacks.
For each softirq there is a per-cpu list head which is where the work
is queued up.
If the platform doesn't support the generic SMP call function bits,
the work is queued onto the local cpu.
The first patch adds a NR_SOFTIRQS so that we can size these arrays
by the actual number of softirqs instead of the magic number "32"
which is what is used now.
The second patch adds the infrastructure and provides intefaces to
invoke softirqs on remove cpus.
Jen's, as stated, has block layer uses for this. I intend to use this
for receive side flow seperation on non-multiqueue network cards. And
Steffen Klassert has a set of IPSEC parallelization changes that can
very likely make use of this.
These patches are against current 2.6.27-rcX
I would suggest that if nobody has any problems with this, we put it
into a GIT tree on kernel.org and any subsystem that wants to use it
can just pull that tree into their GIT tree. This way, it doesn't
matter which tree Linus pulls in first, he'll get this stuff properly
regardless of ordering.
next reply other threads:[~2008-09-20 6:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-20 6:48 David Miller [this message]
2008-09-20 15:29 ` [PATCH 0/2]: Remote softirq invocation infrastructure Daniel Walker
2008-09-20 15:45 ` Arjan van de Ven
2008-09-20 16:02 ` Daniel Walker
2008-09-20 16:19 ` Arjan van de Ven
2008-09-20 17:40 ` Daniel Walker
2008-09-20 18:09 ` Arjan van de Ven
2008-09-20 18:52 ` Daniel Walker
2008-09-20 20:04 ` David Miller
2008-09-20 19:59 ` David Miller
2008-09-21 6:05 ` Herbert Xu
2008-09-21 6:57 ` David Miller
2008-09-22 10:36 ` Ilpo Järvinen
2008-09-24 4:54 ` Herbert Xu
2008-09-21 9:13 ` James Courtier-Dutton
2008-09-21 9:17 ` David Miller
2008-09-21 9:46 ` Steffen Klassert
2008-09-22 8:23 ` Herbert Xu
2008-09-22 13:54 ` Steffen Klassert
2008-09-20 20:00 ` David Miller
2008-09-22 21:22 ` Chris Friesen
2008-09-22 22:12 ` David Miller
2008-09-23 17:03 ` Chris Friesen
2008-09-23 21:10 ` Tom Herbert
2008-09-23 21:51 ` David Miller
2008-09-24 7:42 ` David Miller
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=20080919.234824.223177211.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.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;
as well as URLs for NNTP newsgroup(s).