From: Chris Penney <cpenney@gmail.com>
To: nfs@lists.sourceforge.net
Subject: Use of SMP on NFS server
Date: Thu, 24 Mar 2005 22:39:15 -0500 [thread overview]
Message-ID: <111aefd050324193972d1a5eb@mail.gmail.com> (raw)
I've heard from some that there are issues with NFS + SMP when using
the 2.6 kernel. Assuming I'm using 2.6.11.5 w/ the NFS-ALL patches
applied should I be concerned about running SMP (dual cpu pentium 4
doing pretty much only NFSv3 TCP, but looking toward NFSv4)?
Assuming it's ok to use SMP on a heavy use NFS server, should I enable
or disable hyperthreading? I'd assume that for NFS hyperthreading
would be good, but that's only a guess.
Chris
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
reply other threads:[~2005-03-25 3:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=111aefd050324193972d1a5eb@mail.gmail.com \
--to=cpenney@gmail.com \
--cc=nfs@lists.sourceforge.net \
--cc=penney@msu.edu \
/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