All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Philip Roper <u3205097@anu.edu.au>
To: linux-fsdevel@vger.kernel.org, James Roper <u3205097@anu.edu.au>
Subject: readpages and network file systems
Date: Tue, 12 Oct 2004 12:10:05 +1000	[thread overview]
Message-ID: <416B3CFD.1070505@anu.edu.au> (raw)

Hi

Am I right in saying that the kernel has a maximum of 128K readpages?  I 
saw some discussion in the archives relating to the efficiency of reads 
that size in the context of block devices, and a lot of people were 
saying that reads shouldn't be larger than that because of various 
problems, but what about network file systems?  I'm implementing read 
ahead routines in cifs, and i think reads in the megabytes could greatly 
increase bandwidth utilisation, as you can have up to 50 cifs requests 
of 64K each on the wire at any one time.  The larger the reads, the less 
the round trip time has effect.

Please CC any responses to me as I am not on the mailing list.

James

             reply	other threads:[~2004-10-12  2:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-12  2:10 James Philip Roper [this message]
2004-10-12 16:36 ` readpages and network file systems Sonny Rao

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=416B3CFD.1070505@anu.edu.au \
    --to=u3205097@anu.edu.au \
    --cc=linux-fsdevel@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 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.