From: "saeed bishara" <saeed.bishara@gmail.com>
To: "Jeff Garzik" <jeff@garzik.org>
Cc: linux-kernel@vger.kernel.org, "NFS list" <linux-nfs@vger.kernel.org>
Subject: Re: read-ahead in NFS server
Date: Thu, 27 Dec 2007 17:38:57 +0200 [thread overview]
Message-ID: <c70ff3ad0712270738v2551224ft5694a5673c37aa3c@mail.gmail.com> (raw)
In-Reply-To: <4773BFBA.70709@garzik.org>
>
> I bet
> TCP + fewer revalidations + greater local pagecache activity
> uses less cpu power than
> UDP + revalidations + rx/tx network activity
what do you mean by revalidations?
the workload of the client going to be large sequential IO's, so does
the local pagecache is necessary for this case?
saeed
next prev parent reply other threads:[~2007-12-27 15:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-26 11:51 saeed bishara
2007-12-27 2:34 ` Jeff Garzik
2007-12-27 8:50 ` saeed bishara
2007-12-27 11:54 ` Jeff Garzik
2007-12-27 15:00 ` saeed bishara
2007-12-27 15:07 ` Jeff Garzik
2007-12-27 15:38 ` saeed bishara [this message]
[not found] ` <E1J852H-0002K7-P1@localhost>
2007-12-28 2:33 ` Fengguang Wu
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=c70ff3ad0712270738v2551224ft5694a5673c37aa3c@mail.gmail.com \
--to=saeed.bishara@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
/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
all inboxes | Powered by JetHome®