From: Christoph Hellwig <hch@infradead.org>
To: "David S. Miller" <davem@redhat.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
anton@samba.org, kuznet@ms2.inr.ac.ru, netdev@oss.sgi.com
Subject: Re: net/core/flow.c cpu handling?
Date: Mon, 3 Nov 2003 15:11:45 +0000 [thread overview]
Message-ID: <20031103151145.A29287@infradead.org> (raw)
In-Reply-To: <20031101225050.4de96a8b.davem@redhat.com>; from davem@redhat.com on Sat, Nov 01, 2003 at 10:50:50PM -0800
On Sat, Nov 01, 2003 at 10:50:50PM -0800, David S. Miller wrote:
>
> 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.
Well, the current code is wrong for 2.6 and breaks badly for machines
with more than 32/64 cpus.
--
Christoph Hellwig <hch@lst.de> - Freelance Hacker
Contact me for driver hacking and kernel development consulting
next prev parent reply other threads:[~2003-11-03 15:11 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
2003-11-03 22:45 ` David S. Miller
2003-11-03 15:11 ` Christoph Hellwig [this message]
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=20031103151145.A29287@infradead.org \
--to=hch@infradead.org \
--cc=anton@samba.org \
--cc=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@oss.sgi.com \
--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 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.