From: Mike Snitzer <snitzer@redhat.com>
To: dm-devel@redhat.com
Cc: ejt@redhat.com
Subject: Re: dm thin: set {minimum, optimal}_io_size to pool's data block size
Date: Fri, 18 Jul 2014 18:26:34 -0400 [thread overview]
Message-ID: <20140718222634.GA7755@redhat.com> (raw)
In-Reply-To: <1405720783-7904-1-git-send-email-snitzer@redhat.com>
On Fri, Jul 18 2014 at 5:59pm -0400,
Mike Snitzer <snitzer@redhat.com> wrote:
> Before if the block layer's limit stacking didn't establish an
...
I revised this header when staging for 3.17 in for-next, see:
https://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=for-next&id=a99c223c2a88aeb404afaa1bfce91eb0dd36b80b
prev parent reply other threads:[~2014-07-18 22:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 21:59 [PATCH] dm thin: set {minimum, optimal}_io_size to pool's data block size Mike Snitzer
2014-07-18 22:26 ` Mike Snitzer [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=20140718222634.GA7755@redhat.com \
--to=snitzer@redhat.com \
--cc=dm-devel@redhat.com \
--cc=ejt@redhat.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