From: djani22@dynamicweb.hu
To: David Greaves <david@dgreaves.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID5 question.
Date: Thu, 4 Aug 2005 17:45:21 +0200 [thread overview]
Message-ID: <025301c5990b$8b456cc0$0400a8c0@LocalHost> (raw)
In-Reply-To: 42F22C8F.4000407@dgreaves.com
Thanks a lot for you, and Raz!
The raw devices readahead I already set with the hdparm, and
/sys/block/*/queue/read_ahead_kb, but the md device is only changeable with
blockdev. :-)
I dont use lvm, because it is too slow for me....
But unfortunately the problem is still here for me. :(
I continue searching the bottleneck...
Thanks!
Janos
----- Original Message -----
From: "David Greaves" <david@dgreaves.com>
To: "Raz Ben Jehuda" <razb@bitband.com>
Cc: <djani22@dynamicweb.hu>; <linux-raid@vger.kernel.org>
Sent: Thursday, August 04, 2005 4:56 PM
Subject: Re: RAID5 question.
> And notice you can apply different readahead to:
> The raw devices (/dev/sda)
> The md device (/dev/mdX)
> Any lvm device (/dev/lvm_name/lvm_device)
>
> David
>
> Raz Ben Jehuda wrote:
>
> >read the blockdev man page
> >
> >On Thu, 2005-08-04 at 16:06 +0200, djani22@dynamicweb.hu wrote:
> >
> >
> >>Hi list, Neil!
> >>
> >>I have a little question because I'v got some performance problem...
> >>Is the RAID5 do any type of headahead with the default config?
> >>It is possible to disable the readahead? (if it is.)
> >>Or just the io_sched do that on the disks?
> >>
> >>How can I disable the whole headahead on top of the RAID5 array?
> >>
> >>The RAID5 can do multiple small (<4kb) reads of disks for the
multithreaded
> >>read requests?
> >>(chunk size is 32k)
> >>
> >>Thanks for helping!
> >>
> >>Janos
> >>
> >>-
> >>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
> >>
> >>
>
>
> --
>
> -
> 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
next prev parent reply other threads:[~2005-08-04 15:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-04 5:43 ANNOUNCE: mdadm 2.0-devel-3 DEVELOPMENT RELEASE - A tool for managing Soft RAID under Linux Neil Brown
[not found] ` <01f001c598fd$c59a51a0$0400a8c0@LocalHost>
[not found] ` <1123164866.8854.0.camel@localhost.localdomain>
2005-08-04 14:56 ` RAID5 question David Greaves
2005-08-04 15:45 ` djani22 [this message]
2005-08-04 15:56 ` Raz Ben Jehuda
2005-08-04 16:13 ` djani22
2005-08-04 16:25 ` Raz Ben Jehuda
2005-08-04 16:43 ` djani22
2005-08-04 20:53 ` Neil Brown
2005-08-07 11:40 ` David Greaves
-- strict thread matches above, loose matches on Subject: below --
2003-03-22 12:10 raid5 question Gabriele Alberti
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='025301c5990b$8b456cc0$0400a8c0@LocalHost' \
--to=djani22@dynamicweb.hu \
--cc=david@dgreaves.com \
--cc=linux-raid@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.