From: Andrew Theurer <habanero@us.ibm.com>
To: "David S. Miller" <davem@redhat.com>, neilb@cse.unsw.edu.au
Cc: taka@valinux.co.jp, linux-kernel@vger.kernel.org,
nfs@lists.sourceforge.net
Subject: Re: [PATCH] zerocopy NFS for 2.5.36
Date: Wed, 16 Oct 2002 10:04:27 -0500 [thread overview]
Message-ID: <200210161004.27314.habanero@us.ibm.com> (raw)
In-Reply-To: <20021015.213102.80213000.davem@redhat.com>
On Tuesday 15 October 2002 11:31 pm, David S. Miller wrote:
> From: Neil Brown <neilb@cse.unsw.edu.au>
> Date: Wed, 16 Oct 2002 13:44:04 +1000
>
> Presumably on a sufficiently large SMP machine that this became an
> issue, there would be multiple NICs. Maybe it would make sense to
> have one udp socket for each NIC. Would that make sense? or work?
> It feels to me to be cleaner than one for each CPU.
>
> Doesn't make much sense.
>
> Usually we are talking via one IP address, and thus over
> one device. It could be using multiple NICs via BONDING,
> but that would be transparent to anything at the socket
> level.
>
> Really, I think there is real value to making the socket
> per-cpu even on a 2 or 4 way system.
I am trying my best today to get a 4 way system up and running for this test.
IMO, per cpu is best.. with just one socket, I seriously could not get over
33% cpu utilization on a 4 way (back in April). With TCP, I could max it
out. I'll update later today hopefully with some promising results.
-Andrew
next prev parent reply other threads:[~2002-10-16 15:11 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-18 8:14 Hirokazu Takahashi
2002-09-18 23:00 ` David S. Miller
2002-09-18 23:54 ` Alan Cox
2002-09-19 0:16 ` Andrew Morton
2002-09-19 2:13 ` Aaron Lehmann
2002-09-19 3:30 ` Andrew Morton
2002-09-19 10:42 ` Alan Cox
2002-09-19 13:15 ` [NFS] " Hirokazu Takahashi
2002-09-19 20:42 ` Andrew Morton
2002-09-19 21:12 ` David S. Miller
2002-09-21 11:56 ` Pavel Machek
2002-10-14 5:50 ` Neil Brown
2002-10-14 6:15 ` David S. Miller
2002-10-14 10:45 ` kuznet
2002-10-14 10:48 ` David S. Miller
2002-10-14 12:01 ` Hirokazu Takahashi
2002-10-14 14:12 ` Andrew Theurer
2002-10-16 3:44 ` Neil Brown
2002-10-16 4:31 ` David S. Miller
2002-10-16 15:04 ` Andrew Theurer [this message]
2002-10-17 2:03 ` [NFS] " Andrew Theurer
2002-10-17 2:31 ` Hirokazu Takahashi
2002-10-17 13:16 ` Andrew Theurer
2002-10-17 13:26 ` Hirokazu Takahashi
2002-10-17 14:10 ` Andrew Theurer
2002-10-17 16:26 ` Hirokazu Takahashi
2002-10-18 5:38 ` Trond Myklebust
2002-10-18 7:19 ` Hirokazu Takahashi
2002-10-18 15:12 ` Andrew Theurer
2002-10-19 20:34 ` Hirokazu Takahashi
2002-10-22 21:16 ` Andrew Theurer
2002-10-23 9:29 ` Hirokazu Takahashi
2002-10-24 15:32 ` Andrew Theurer
2002-10-16 11:09 ` Hirokazu Takahashi
2002-10-16 17:02 ` kaza
2002-10-17 4:36 ` rddunlap
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=200210161004.27314.habanero@us.ibm.com \
--to=habanero@us.ibm.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs@lists.sourceforge.net \
--cc=taka@valinux.co.jp \
/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®