From: Rusty Russell <rusty@rustcorp.com.au>
To: "David S. Miller" <davem@redhat.com>
Cc: anton@samba.org, kuznet@ms2.inr.ac.ru, netdev@oss.sgi.com
Subject: Re: net/core/flow.c cpu handling?
Date: Mon, 03 Nov 2003 21:26:40 +1100 [thread overview]
Message-ID: <20031103102829.E1C622C05E@lists.samba.org> (raw)
In-Reply-To: Your message of "Sat, 01 Nov 2003 22:50:50 -0800." <20031101225050.4de96a8b.davem@redhat.com>
In message <20031101225050.4de96a8b.davem@redhat.com> you write:
>
> Very likely, the code is how it is in order to make the
> 2.4.x backport of this code and the 2.6.x version as
> similar as humanly possible.
Hmm, AFAICT the patch I sent should be easier, not harder to backport.
Anyway, I'm carrying the patch as part of the hotplug CPU patches: we
can discuss it once 2.6.0 is out.
Thanks,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2003-11-03 10:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-02 6:22 net/core/flow.c cpu handling? Rusty Russell
2003-11-02 6:50 ` David S. Miller
2003-11-03 10:26 ` Rusty Russell [this message]
2003-11-03 22:45 ` David S. Miller
2003-11-03 15:11 ` Christoph Hellwig
2003-11-03 22:55 ` David S. 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=20031103102829.E1C622C05E@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=anton@samba.org \
--cc=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.