All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: saeed bishara <saeed.bishara@gmail.com>
Cc: linux-kernel@vger.kernel.org, NFS list <linux-nfs@vger.kernel.org>
Subject: Re: read-ahead in NFS server
Date: Wed, 26 Dec 2007 21:34:23 -0500	[thread overview]
Message-ID: <47730F2F.3080900@garzik.org> (raw)
In-Reply-To: <c70ff3ad0712260351i6583aa8dpbf16ed606a634b1f-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

saeed bishara wrote:
> Hi,
> my NFS server seems not to utilize the read-ahead feature, my exported
> dir is located on ext3 fs over sata disk. the sata controller can
> issue commands up to 1MB, also I modified the read ahead under the sys
> to 1MB. but when the client do reads in 32KB chunks (rsize), I can see
> in the server side that all IOs are ~32KB. my kernel version is
> 2.6.22.7.
> according to the nfsd code, the NFS server should utilize the
> read-ahead feature, but what should I do
> to make it work?

(linux-nfs added to cc)

I cannot speak for the NFS server code specifically, but 32kb sounds 
like a network read (or write) data size limit.

Are you using TCP?  Are you using NFSv4, or an older version?

	Jeff



WARNING: multiple messages have this Message-ID (diff)
From: Jeff Garzik <jeff@garzik.org>
To: saeed bishara <saeed.bishara@gmail.com>
Cc: linux-kernel@vger.kernel.org, NFS list <linux-nfs@vger.kernel.org>
Subject: Re: read-ahead in NFS server
Date: Wed, 26 Dec 2007 21:34:23 -0500	[thread overview]
Message-ID: <47730F2F.3080900@garzik.org> (raw)
In-Reply-To: <c70ff3ad0712260351i6583aa8dpbf16ed606a634b1f@mail.gmail.com>

saeed bishara wrote:
> Hi,
> my NFS server seems not to utilize the read-ahead feature, my exported
> dir is located on ext3 fs over sata disk. the sata controller can
> issue commands up to 1MB, also I modified the read ahead under the sys
> to 1MB. but when the client do reads in 32KB chunks (rsize), I can see
> in the server side that all IOs are ~32KB. my kernel version is
> 2.6.22.7.
> according to the nfsd code, the NFS server should utilize the
> read-ahead feature, but what should I do
> to make it work?

(linux-nfs added to cc)

I cannot speak for the NFS server code specifically, but 32kb sounds 
like a network read (or write) data size limit.

Are you using TCP?  Are you using NFSv4, or an older version?

	Jeff



  parent reply	other threads:[~2007-12-27  2:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-26 11:51 read-ahead in NFS server saeed bishara
     [not found] ` <c70ff3ad0712260351i6583aa8dpbf16ed606a634b1f-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-12-27  2:34   ` Jeff Garzik [this message]
2007-12-27  2:34     ` Jeff Garzik
2007-12-27  8:50     ` saeed bishara
     [not found]       ` <c70ff3ad0712270050u134616d1q459ed073c586dcec-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-12-27 11:54         ` Jeff Garzik
2007-12-27 11:54           ` Jeff Garzik
2007-12-27 15:00           ` saeed bishara
     [not found]             ` <c70ff3ad0712270700h6336b194r7c21834423aeb331-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-12-27 15:07               ` Jeff Garzik
2007-12-27 15:07                 ` Jeff Garzik
2007-12-27 15:38                 ` saeed bishara
2007-12-28  2:33               ` Fengguang Wu
2007-12-28  2:33                 ` Fengguang Wu
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=47730F2F.3080900@garzik.org \
    --to=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=saeed.bishara@gmail.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.