From: Jim Rees <rees@umich.edu>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-nfs@vger.kernel.org, peter honeyman <honey@citi.umich.edu>,
sfaibish <sfaibish@emc.com>
Subject: Re: Block layout rpm
Date: Mon, 29 Nov 2010 17:26:13 -0500 [thread overview]
Message-ID: <20101129222613.GA1210@merit.edu> (raw)
In-Reply-To: <4CF4249F.9070400@garzik.org>
Jeff Garzik wrote:
"pNFS will work with 32-bit linux and lesser hardware, but the you
will not obtain the performance benefits of pNFS."
That's just silly, and, I might even go so far as to say "wrong".
The benefits of direct-to-storage access, without an MDS middle-man,
are quite noticable even for 32-bit, underpowered, and/or embedded
clients.
Agreed. It used to say 64-bit only, and I added the part about 32-bit
because it does run on 32-bit, but really that should just come out. I'll
fix it.
next prev parent reply other threads:[~2010-11-29 22:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 21:07 Block layout rpm Jim Rees
2010-11-29 22:09 ` Jeff Garzik
2010-11-29 22:26 ` Jim Rees [this message]
2010-11-29 22:39 ` Jeff Garzik
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=20101129222613.GA1210@merit.edu \
--to=rees@umich.edu \
--cc=honey@citi.umich.edu \
--cc=jeff@garzik.org \
--cc=linux-nfs@vger.kernel.org \
--cc=sfaibish@emc.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;
as well as URLs for NNTP newsgroup(s).