From: Matthew Wilcox <willy@debian.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: "David S. Miller" <davem@redhat.com>,
george@mvista.com, willy@debian.org, kuznet@ms2.inr.ac.ru,
linux-kernel@vger.kernel.org
Subject: Re: softirq parameters
Date: Wed, 7 Aug 2002 19:23:14 +0100 [thread overview]
Message-ID: <20020807192314.H24631@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20020807152423.3577a5cc.rusty@rustcorp.com.au>; from rusty@rustcorp.com.au on Wed, Aug 07, 2002 at 03:24:23PM +1000
On Wed, Aug 07, 2002 at 03:24:23PM +1000, Rusty Russell wrote:
> Partially agree. Removing all args might be worthwhile. But all these
> softirqs use the "cpu" arg to access per-cpu data, which should be
> changed to use the per_cpu_data mechanism anyway, which removes the
> point of the arg.
I see. That makes a lot of sense.
> Things haven't been changed over because I haven't pushed the per-cpu
> interface changes (required for some archs 8() to Linus yet. But you'll
> want them so we can save space (you only need allocate per-cpu data for
> cpus where cpu_possible(i) is true).
So what we want is something more like:
struct softnet_data softnet_data __per_cpu_data = { NULL };
static void void net_tx_action(void *arg)
{
struct softnet_data *data = arg;
if (arg->completion_queue) {
...
}
open_softirq(NET_TX_SOFTIRQ, net_tx_action, softnet_data);
and have kernel/softirq.c do:
do {
if (pending & 1)
h->action(this_cpu(h->data));
h++;
pending >>= 1;
} while (pending);
right?
--
Revolutions do not require corporate support.
next prev parent reply other threads:[~2002-08-07 18:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-04 16:26 Matthew Wilcox
2002-08-04 17:38 ` george anzinger
2002-08-05 5:37 ` David S. Miller
2002-08-07 5:24 ` Rusty Russell
2002-08-07 18:23 ` Matthew Wilcox [this message]
2002-08-07 18:18 ` David S. Miller
2002-08-07 18:35 ` Matthew Wilcox
2002-08-07 18:24 ` David S. Miller
2002-08-08 2:29 ` Rusty Russell
2002-08-08 5:13 ` 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=20020807192314.H24631@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=davem@redhat.com \
--cc=george@mvista.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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
all inboxes | Powered by JetHome®