linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: linux-scsi@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [PATCH 0 of 3] [RFC] I/O Hints
Date: Thu, 05 Jun 2008 01:22:49 -0400	[thread overview]
Message-ID: <patchbomb.1212643369@sermon.lab.mkp.net> (raw)

This is just a proof of concept set of patches.  I'd like some
feedback before I spend more time on them.

At the Filesystem & Storage Workshop there was lots of discussion
about how to communicate I/O alignment, stripe width, etc. to the
filesystems so they could lay out things properly.

An addition to the up-and-coming version of the SCSI block protocol
features an inquiry page that hardware RAIDs can use to indicate
preferred I/O sizes for a given LUN.

This patch kit implements support for exporting those values in
/sys/block/.  I have implemented support for it in sd.c using the
Block Limits VPD and in MD using chunk size and stripe width.

The physical sector offset for the start of the "virtual" block device
is also exported.  This includes partitions so you can get the actual
physical start sector offset for - say - an MD device sitting on a
partitioned set of drives.

Comments and suggestions are welcome.

-- 
Martin K. Petersen	Oracle Linux Engineering




             reply	other threads:[~2008-06-05  5:24 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-05  5:22 Martin K. Petersen [this message]
2008-06-05  5:22 ` [PATCH 1 of 3] block: Export I/O hints for block devices and partitions Martin K. Petersen
2008-06-05 14:42   ` James Bottomley
2008-06-06  1:18     ` Martin K. Petersen
2008-06-06 14:21   ` Jamie Lokier
2008-06-05  5:22 ` [PATCH 2 of 3] md: Export preferred I/O sizes and physical alignment Martin K. Petersen
2008-06-05  5:22 ` [PATCH 3 of 3] sd: Export preferred I/O sizes Martin K. Petersen
2008-06-05 11:25   ` Boaz Harrosh
2008-06-05  6:27 ` [PATCH 0 of 3] [RFC] I/O Hints Andreas Dilger
2008-06-05 10:32   ` Jamie Lokier
2008-06-05 12:35   ` Matthew Wilcox
2008-06-05 17:02     ` Dan Williams
2008-06-06  1:03   ` Martin K. Petersen
2008-06-06 14:02     ` Jamie Lokier
2008-06-06 16:48       ` Martin K. Petersen
2008-06-09 10:47         ` Jamie Lokier
2008-06-10  2:17           ` Martin K. Petersen
2008-06-05 10:40 ` Jamie Lokier
2008-06-05 19:19   ` Andreas Dilger
2008-06-06 12:55     ` Jamie Lokier
2008-06-06  1:16   ` Martin K. Petersen
2008-06-06  4:51     ` Dave Chinner
2008-06-06 16:53       ` Martin K. Petersen
2008-06-07 20:54         ` Dave Chinner
2008-06-09 15:05           ` Martin K. Petersen
2008-06-06 12:52     ` Jamie Lokier
2008-06-06 14:26 ` Jamie Lokier
2008-06-06 16:56   ` Martin K. Petersen

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=patchbomb.1212643369@sermon.lab.mkp.net \
    --to=martin.petersen@oracle.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-scsi@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 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).