All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: xfs@oss.sgi.com
Subject: Re: Pid: 8345, comm: rsync Not tainted 2.6.32.22intel #1
Date: Thu, 28 Oct 2010 07:59:55 +1100	[thread overview]
Message-ID: <20101027205955.GB2715@dastard> (raw)
In-Reply-To: <201010271258.45965@zmi.at>

On Wed, Oct 27, 2010 at 12:58:45PM +0200, Michael Monnerie wrote:
> On Mittwoch, 27. Oktober 2010 Dave Chinner wrote:
> > 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.
> 
> Sounds very nice. But the script I use will still work when upgrading 
> the server from openSUSE 11.2 to 11.3, and is therefore the preferred 
> choice for me.
> 
> Also, I'd need to find information and learn how to tweak udev hotplug 
> rules.

GIYF.

> I want to implement this on about 30 VMs on 2 different hosts, 
> with 3 different release states of servers (openSUSE 11.1, 11.2 and 
> 11.3).

The udev rule format hasn't changed in a long while. The same rule
set should work on all of these.

> The chance is high that I'd need two or three different udev 
> tweaks for the different releases, so I don't see the benefit of udev 
> for me. I wrote the script in about the same time I wrote this mail.

You'd need one regex per device type you want to tweak with
different values.

> That's always the problem between developers ("ah, cool new stuff") and 
> admins ("i need this on 500 servers with least possible work for me, and 
> it must still work after any updates/upgrades").

This is not "cool new stuff" - I've seen it used for exactly this
purpose for _several years_ by distros. e.g. pulling the identifier
string from the device to set hardware device specific tunables,
changing default dm/md readahead, etc. It's not new, and is easy to
configure generically so it works on a wide array of different machines.

And if you hotplug devices, it just works automatically - you don't
need to rerun a script after every hotplug...

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2010-10-27 20:58 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
2010-10-27 10:58                   ` Michael Monnerie
2010-10-27 20:59                     ` Dave Chinner [this message]
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=20101027205955.GB2715@dastard \
    --to=david@fromorbit.com \
    --cc=michael.monnerie@is.it-management.at \
    --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 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.