From: Neil Brown <neilb@suse.de>
To: Mike Snitzer <snitzer@redhat.com>
Cc: jens.axboe@oracle.com,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: md: Use new topology calls to indicate alignment and I/O sizes
Date: Wed, 1 Jul 2009 09:58:32 +1000 [thread overview]
Message-ID: <19018.42664.764760.682918@notabene.brown> (raw)
In-Reply-To: message from Mike Snitzer on Tuesday June 30
On Tuesday June 30, snitzer@redhat.com wrote:
>
> Neil,
>
> Any chance you could make a formal pull request for this MD topology
> support patch for 2.6.31-rc2?
Yes.. I want to include a couple of other patches in the same batch
and I've been a bit distracted lately (by a cold among other things).
I'll try to get this sorted out today.
>
> NOTE: all the disk_stack_limits() calls must pass the 3rd 'offset' arg
> in terms of bytes and _not_ sectors. So all of MD's calls to
> disk_stack_limits() should pass: rdev->data_offset << 9
Noted, thanks.
NeilBrown
prev parent reply other threads:[~2009-06-30 23:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 4:54 [PATCH] md: Use new topology calls to indicate alignment and I/O sizes Martin K. Petersen
2009-06-23 21:44 ` Mike Snitzer
2009-06-24 4:05 ` Neil Brown
2009-06-24 5:03 ` Martin K. Petersen
2009-06-24 6:22 ` Neil Brown
2009-06-24 15:27 ` Mike Snitzer
2009-06-24 16:27 ` Mike Snitzer
2009-06-24 23:28 ` Neil Brown
2009-06-25 0:05 ` Martin K. Petersen
2009-06-24 17:07 ` [PATCH] " Martin K. Petersen
2009-06-25 2:35 ` Neil Brown
2009-06-25 4:37 ` Martin K. Petersen
2009-06-25 6:16 ` Neil Brown
2009-06-25 16:24 ` Martin K. Petersen
2009-06-30 20:24 ` Mike Snitzer
2009-06-30 23:58 ` 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.42664.764760.682918@notabene.brown \
--to=neilb@suse.de \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@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).