From: Dave Chinner <david@fromorbit.com>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>, xfs@oss.sgi.com
Subject: Re: Pid: 8345, comm: rsync Not tainted 2.6.32.22intel #1
Date: Wed, 27 Oct 2010 14:55:48 +1100 [thread overview]
Message-ID: <20101027035548.GD32255@dastard> (raw)
In-Reply-To: <201010270124.44846@zmi.at>
On Wed, Oct 27, 2010 at 01:23:35AM +0200, Michael Monnerie wrote:
> On Dienstag, 26. Oktober 2010 Emmanuel Florac wrote:
> > echo "noop" > /sys/block/sdc/queue/scheduler
> > echo 512 > /sys/block/sdc/queue/nr_requests
> > blockdev --setra 4096 /dev/sdc
>
> How about this small script in /etc/init.d/boot.local?
>
> for i in /dev/xvd? /dev/sd? ; do
> if test "$i" == "${i%\?}" ; then
> echo i=$i
> blockdev --setra 1024 $i
> j=${i#/dev/}
> echo j=$j
> echo noop >/sys/block/$j/queue/scheduler
> echo 512 >/sys/block/$j/queue/nr_requests
> fi
> done
>
> This works for VMs within XenServer (/dev/xvda) and real servers
> (/dev/sda), and sets some values for all drives.
I'd suggest that people learn how to tweak udev hotplug rules so
that when the device is first created (i.e. during hotplug) the
scheduler, queue depth and readahead are set automatically. That way
you don't have to rely on devices being discovered before your script
runs...
Another benefit of doing it this way is that it is easy to set
default rules for different types of devices based on regex matching
e.g. different configs for "sd*" vs "dm*" vs "vd*" are trivial to
set up.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-10-27 3:54 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 6:25 Pid: 8345, comm: rsync Not tainted 2.6.32.22intel #1 Stefan Priebe - Profihost AG
2010-10-26 7:22 ` Emmanuel Florac
2010-10-26 7:24 ` Stefan Priebe - Profihost AG
2010-10-26 7:41 ` Emmanuel Florac
2010-10-26 7:53 ` Stefan Priebe - Profihost AG
2010-10-26 11:01 ` Emmanuel Florac
2010-10-26 11:03 ` Stefan Priebe - Profihost AG
2010-10-26 11:25 ` Emmanuel Florac
2010-10-26 12:09 ` Stefan Priebe - Profihost AG
2010-10-26 13:00 ` Emmanuel Florac
2010-10-26 23:23 ` Michael Monnerie
2010-10-27 3:55 ` Dave Chinner [this message]
2010-10-27 10:58 ` Michael Monnerie
2010-10-27 20:59 ` Dave Chinner
2010-10-28 9:39 ` Michael Monnerie
2010-10-27 6:04 ` Emmanuel Florac
2010-10-27 7:00 ` Stefan Priebe - Profihost AG
2010-10-27 10:06 ` Emmanuel Florac
2010-10-27 10:08 ` Stefan Priebe - Profihost AG
2010-10-27 10:12 ` Emmanuel Florac
2010-10-27 10:22 ` Stefan Priebe - Profihost AG
2010-10-27 11:14 ` Emmanuel Florac
2010-10-26 11:30 ` Larsen, Tore Høivaag
2010-10-26 11:47 ` Emmanuel Florac
2010-11-01 8:01 ` Stefan Priebe - Profihost AG
2010-11-01 10:11 ` Emmanuel Florac
2010-11-01 10:28 ` Stefan Priebe - Profihost AG
2010-11-01 12:27 ` Dave Chinner
2010-11-01 12:28 ` Stefan Priebe - Profihost AG
2010-11-01 12:52 ` Dave Chinner
2010-11-01 13:29 ` Emmanuel Florac
2010-11-01 13:48 ` Stefan Priebe - Profihost AG
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=20101027035548.GD32255@dastard \
--to=david@fromorbit.com \
--cc=michael.monnerie@is.it-management.at \
--cc=s.priebe@profihost.ag \
--cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox