From: "Andrew Theurer" <habanero@us.ibm.com>
To: <neilb@cse.unsw.edu.au>, "David S. Miller" <davem@redhat.com>
Cc: <taka@valinux.co.jp>, <linux-kernel@vger.kernel.org>,
<nfs@lists.sourceforge.net>
Subject: Re: [NFS] Re: [PATCH] zerocopy NFS for 2.5.36
Date: Wed, 16 Oct 2002 21:03:33 -0500 [thread overview]
Message-ID: <012d01c27581$677d2180$2a060e09@beavis> (raw)
In-Reply-To: 20021015.213102.80213000.davem@redhat.com
> 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 still seeing some sort of problem on an 8 way (hyperthreaded 8
logical/4 physical) on UDP with these patches. I cannot get more than 2
NFSd threads in a run state at one time. TCP usually has 8 or more. The
test involves 40 100Mbit clients reading a 200 MB file on one server (4
acenic adapters) in cache. I am fighting some other issues at the moment
(acpi wierdness), but so far before the patches, 82 MB/sec for NFSv2,UDP and
138 MB/sec for NFSv2,TCP. With the patches, 115 MB/sec for NFSv2,UDP and
181 MB/sec for NFSv2,TCP. One CPU is maxed due to acpi int storm, so I
think the results will get better. I'm not sure what other lock or
contention point this is hitting on UDP. If there is anything I can do to
help, please let me know, thanks.
Andrew Theurer
next prev parent reply other threads:[~2002-10-17 1:51 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-18 8:14 [PATCH] zerocopy NFS for 2.5.36 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
2002-10-17 2:03 ` Andrew Theurer [this message]
2002-10-17 2:31 ` [NFS] " 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
-- strict thread matches above, loose matches on Subject: below --
2002-09-19 2:00 [NFS] " Lever, Charles
[not found] <3D89176B.40FFD09B@digeo.com.suse.lists.linux.kernel>
[not found] ` <20020919.221513.28808421.taka@valinux.co.jp.suse.lists.linux.kernel>
[not found] ` <3D8A36A5.846D806@digeo.com.suse.lists.linux.kernel>
2002-09-20 1:00 ` Andi Kleen
2002-09-20 1:09 ` Andrew Morton
2002-09-20 1:23 ` Andi Kleen
2002-09-20 1:27 ` David S. Miller
2002-09-20 2:06 ` Andi Kleen
2002-09-20 2:01 ` David S. Miller
2002-09-20 2:28 ` Andi Kleen
2002-09-20 2:20 ` David S. Miller
2002-09-20 2:35 ` Andi Kleen
2002-10-16 14:04 Lever, Charles
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='012d01c27581$677d2180$2a060e09@beavis' \
--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;
as well as URLs for NNTP newsgroup(s).