From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "Tom Sightler" <ttsig@tuxyturvy.com>
Cc: "Linux-Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: NFS Client and SMP
Date: 29 Aug 2001 10:57:28 +0200 [thread overview]
Message-ID: <shsae0jtf9j.fsf@charged.uio.no> (raw)
In-Reply-To: <Pine.LNX.4.05.10108281806180.20438-100000@lara.stud.fh-heilbronn.de> <shsk7zongjw.fsf@charged.uio.no> <001d01c13004$61965890$70751a0a@zeusinc.com>
In-Reply-To: "Tom Sightler"'s message of "Tue, 28 Aug 2001 16:59:48 -0400"
>>>>> " " == Tom Sightler <ttsig@tuxyturvy.com> writes:
> Is this problem specific to the 2.4 series or is the 2.2 NFS
> implementation suspect to this as well. I am curious because
> we have a good number of SMP servers running SuSE's 2.2.19
> kernel connected to a NetApp filer via GigE with jumbo frames
> and have not had any problems during development. However, we
> are about 1 month from going production and load will increase
> tremendously then (even though we've attempted to stress the
> system in development, real production always introduces new
> loads).
I don't have acces to a test setup for Gigabit, so I have to rely on
other people's reports. I can only remember hearing of problems in
2.4.x, however you might want to check the archives on the NFS
discussion list on Sourceforge.
Cheers,
Trond
next prev parent reply other threads:[~2001-08-29 8:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-28 16:16 NFS Client and SMP Oliver Paukstadt
2001-08-28 18:57 ` Trond Myklebust
2001-08-28 19:13 ` Trond Myklebust
2001-08-28 20:59 ` Tom Sightler
2001-08-29 8:57 ` Trond Myklebust [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-28 16:33 Elgar, Jeremy
2001-08-28 16:47 ` Alan Cox
2001-08-28 16:49 Elgar, Jeremy
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=shsae0jtf9j.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=ttsig@tuxyturvy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox