From: Neil Brown <neilb@suse.de>
To: Andreas Dilger <adilger@sun.com>
Cc: Jens Axboe <jens.axboe@oracle.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Mike Snitzer <snitzer@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Alasdair G Kergon <agk@redhat.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-raid@vger.kernel.org, linux-ide@vger.kernel.org,
linux-fsdevel@vger.kernel.org,
device-mapper development <dm-devel@redhat.com>
Subject: Re: [dm-devel] REQUEST for new 'topology' metrics to be moved out of the 'queue' sysfs directory.
Date: Wed, 1 Jul 2009 10:29:10 +1000 [thread overview]
Message-ID: <19018.44502.425131.683796@notabene.brown> (raw)
In-Reply-To: message from Andreas Dilger on Tuesday June 30
On Tuesday June 30, adilger@sun.com wrote:
> On Jun 29, 2009 13:41 +0200, Jens Axboe wrote:
> > ... externally it just makes the API worse since tools then have to know
> > which device type they are talking to.
> >
> > So I still see absolutely zero point in making such a change, quite the
> > opposite.
>
> Exactly correct. Changing these tunables just for the sake of giving
> them a slightly different name is madness. Making all block devices
> appear more uniform to userspace (even if they don't strictly need all
> of the semantics) is very sensible. The whole point of the kernel is
> to abstract away the underlying details so that userspace doesn't need
> to understand it all again.
Uniformity is certainly desirable. But we shouldn't take it so far
as to make apples look like oranges.
We wouldn't want a SATA disk drive to have 'chunk_size' and 'raid_disks'.
Nor would we want a software RAID array to have a 'scheduler' or
'iosched' attributes.
>
> In order to get good throughput on RAID arrays we need to tune the
> queue/max_* values to ensure the IO requests don't get split.
>
> It would be great if the MD queue/max_* values would pass these tunings
> down to the underlying disk devices as well. As it stands now, we have
> to follow the /sys/block/*/slaves tree to set all of these ourselves,
> and before "slaves/" was introduced it was nigh impossible to automatically
> tune these values.
I don't think that passing these values down is - in general - a well
defined problem. This is (in part) because md/dm devices can be based on
partitions, and partitions don't have independent max_* values.
In your particular case, I don't expect that you use partitions, so it
makes perfect sense to do the tuning on a per-array basis. But I
don't think that it is a concept that fits in the kernel. As you say,
we have 'slaves/', which makes it practical to do this in user-space
and I would rather it stayed there.
NeilBrown
prev parent reply other threads:[~2009-07-01 0:29 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-25 3:58 REQUEST for new 'topology' metrics to be moved out of the 'queue' sysfs directory Neil Brown
2009-06-25 8:00 ` Martin K. Petersen
2009-06-25 11:07 ` [dm-devel] " NeilBrown
2009-06-25 11:36 ` John Robinson
2009-06-25 17:43 ` Martin K. Petersen
2009-06-25 12:17 ` berthiaume_wayne
2009-06-25 17:38 ` Martin K. Petersen
2009-06-25 17:46 ` Linus Torvalds
2009-06-25 19:34 ` Jens Axboe
2009-06-26 11:58 ` [dm-devel] " Neil Brown
2009-06-26 14:48 ` Martin K. Petersen
2009-07-07 1:47 ` [dm-devel] " Neil Brown
2009-07-07 5:29 ` Martin K. Petersen
2009-07-09 0:42 ` Neil Brown
2009-07-07 22:06 ` Bill Davidsen
2009-06-25 19:40 ` [dm-devel] " Jens Axboe
2009-06-26 12:41 ` Neil Brown
2009-06-26 12:50 ` Jens Axboe
2009-06-26 13:16 ` NeilBrown
2009-06-26 13:27 ` Jens Axboe
2009-06-26 13:41 ` NeilBrown
2009-06-26 13:49 ` Jens Axboe
2009-06-27 12:50 ` Neil Brown
2009-06-26 13:23 ` [dm-devel] " NeilBrown
2009-06-26 13:29 ` Jens Axboe
2009-06-27 12:32 ` Neil Brown
2009-06-29 10:18 ` [dm-devel] " Jens Axboe
2009-06-29 10:52 ` NeilBrown
2009-06-29 11:41 ` Jens Axboe
2009-06-29 12:45 ` Boaz Harrosh
2009-06-29 12:52 ` Jens Axboe
2009-06-29 23:09 ` Andreas Dilger
2009-07-01 0:29 ` Neil Brown [this message]
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=19018.44502.425131.683796@notabene.brown \
--to=neilb@suse.de \
--cc=adilger@sun.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=jens.axboe@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=snitzer@redhat.com \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).