From: Andreas Dilger <adilger@clusterfs.com>
To: Simon Matthews <simon@paxonet.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFS Client mis-behaviour?
Date: Mon, 10 Jun 2002 23:14:53 -0600 [thread overview]
Message-ID: <20020611051453.GV20388@turbolinux.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0206102041020.11116-100000@spare>
On Jun 10, 2002 20:48 -0700, Simon Matthews wrote:
> I have seen some strange behaviour from the NFS client.
Sorry, can't help with the NFS problem.
> We installed a new machine, 2 x 2.2GHz Xeon processors
>
> Another question: this system has 2 CPUs, yet the kernel detects 4. Any
> ideas why?
Probably because they are "Hyper Threaded" (HT) CPUs, which means they
have (almost) 2 CPU cores per chip. The second core is not a full CPU,
so it is not as fast as running a 4 CPU system, but reports are about
30% faster than just 2 CPUs.
Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/
next prev parent reply other threads:[~2002-06-11 5:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-11 3:48 NFS Client mis-behaviour? Simon Matthews
2002-06-11 5:14 ` Andreas Dilger [this message]
2002-06-11 14:31 ` Trond Myklebust
2002-06-11 16:28 ` Simon Matthews
2002-06-12 11:57 ` Trond Myklebust
2002-06-12 8:16 ` Alan Cox
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=20020611051453.GV20388@turbolinux.com \
--to=adilger@clusterfs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=simon@paxonet.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 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.