mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "James Stevenson" <mail-lists@stev.org>
To: "Roy Sigurd Karlsbakk" <roy@karlsbakk.net>,
	"Marcelo Tosatti" <marcelo@conectiva.com.br>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: /proc/sys/vm/(max|min)-readahead effect????
Date: Wed, 5 Dec 2001 19:43:57 -0000	[thread overview]
Message-ID: <019401c17dc5$2e946130$0801a8c0@Stev.org> (raw)
In-Reply-To: <Pine.LNX.4.30.0112051917430.3021-100000@mustard.heime.net>



> > Basically you cannot simply expect an increase in readahead size to
> > increase performance:
> >
> > 1) The files you created may not be sequential
>
> Beleive me - they are! Created with 'dd' secuentially

thats still does not mean they are sequential creating
large files almost always causes them to fragment.

Actually does anyone know of an easy way to find out
if certin files are fragmented and by how much ?





  reply	other threads:[~2001-12-05 19:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-05 16:21 Roy Sigurd Karlsbakk
2001-12-05 16:51 ` Marcelo Tosatti
2001-12-05 18:09   ` Roy Sigurd Karlsbakk
2001-12-05 16:58     ` Marcelo Tosatti
2001-12-05 18:20       ` Roy Sigurd Karlsbakk
2001-12-05 19:43         ` James Stevenson [this message]
2001-12-05 20:06           ` Roy Sigurd Karlsbakk
2001-12-05 20:53             ` James Stevenson
2001-12-06 11:45               ` Roy Sigurd Karlsbakk
2001-12-06 18:44               ` Bernd Eckenfels
2001-12-05 18:22   ` Rik van Riel
2001-12-05 18:27     ` Roy Sigurd Karlsbakk
2001-12-06 10:09       ` Martin Dalecki
2001-12-05 20:13 ` Andrew Morton
2001-12-05 20:53   ` Roger Larsson
2001-12-06 11:31   ` Roy Sigurd Karlsbakk
2001-12-06 18:46     ` Bernd Eckenfels
2001-12-07 11:25       ` Roy Sigurd Karlsbakk

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='019401c17dc5$2e946130$0801a8c0@Stev.org' \
    --to=mail-lists@stev.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=roy@karlsbakk.net \
    /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®