All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Greaves <david@dgreaves.com>
To: Stephan van Hienen <raid@a2000.nu>
Cc: linux-raid@vger.kernel.org
Subject: Re: readahead (blockdev --setra) with sw raid(5)?
Date: Sat, 27 Nov 2004 23:52:29 +0000	[thread overview]
Message-ID: <41A9133D.5000809@dgreaves.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0411272328270.16979@adsl.a2000.nu>

I routinely use --setra 4096 on the underlying devices, the md array 
devices and the lvm devices
I am generally reading 1-2 gigabyte files.

I use XFS and it is often suggested as a good fs (though I think there 
may be some XFS/nfs issues with 2.6 at the moment - see lkml)

David

Stephan van Hienen wrote:

> Hi,
>
> just saw a 3ware document with some hints for hardware raid5
> they advice to use blockdev --setra 16384
>
> since i'm not using 3ware hardware raid
> (i'm using 2*7500 3ware's with sw raid5 over 14 disks)
> i'm wondering if --setra can still improve my raid performance
>
> any hints about this ?
> or some other hints, improvements on filesystem ?
> i'm currently using blocksize 128, maybe switching to 256 helps ? 
> (with large files)
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


  reply	other threads:[~2004-11-27 23:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-27 22:31 readahead (blockdev --setra) with sw raid(5)? Stephan van Hienen
2004-11-27 23:52 ` David Greaves [this message]
2004-11-28 10:46   ` Stephan van Hienen
2004-11-30  2:18 ` Neil Brown

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=41A9133D.5000809@dgreaves.com \
    --to=david@dgreaves.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=raid@a2000.nu \
    /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.