From: Jens Axboe <jaxboe@fusionio.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Mike Snitzer <snitzer@redhat.com>,
Lars Ellenberg <lars.ellenberg@linbit.com>,
device-mapper development <dm-devel@redhat.com>,
Mikulas Patocka <mpatocka@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Alasdair G Kergon <agk@redhat.com>,
"stable@kernel.org" <stable@kernel.org>
Subject: Re: [PATCH for-2.6.37] block: max hardware sectors limit wrapper
Date: Fri, 17 Dec 2010 08:34:51 +0100 [thread overview]
Message-ID: <4D0B129B.3070500@fusionio.com> (raw)
In-Reply-To: <yq1wrn92s8x.fsf@sermon.lab.mkp.net>
On 2010-12-17 00:49, Martin K. Petersen wrote:
>>>>>> "Mike" == Mike Snitzer <snitzer@redhat.com> writes:
>
> Mike> Implement blk_limits_max_hw_sectors() and make
> Mike> blk_queue_max_hw_sectors() a wrapper around it.
>
> Mike> DM needs this to avoid setting queue_limits' max_hw_sectors and
> Mike> max_sectors directly. dm_set_device_limits() now leverages
> Mike> blk_limits_max_hw_sectors() logic to establish the appropriate
> Mike> max_hw_sectors minimum (PAGE_SIZE). Fixes issue where DM was
> Mike> incorrectly setting max_sectors rather than max_hw_sectors (which
> Mike> caused dm_merge_bvec()'s max_hw_sectors check to be ineffective).
>
> Acked-by: Martin K. Petersen <martin.petersen@oracle.com>
>
> Jens, please apply.
Thanks, it's in.
--
Jens Axboe
prev parent reply other threads:[~2010-12-17 7:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 18:43 [PATCH for-2.6.37] block: max hardware sectors limit wrapper Mike Snitzer
2010-12-16 23:49 ` Martin K. Petersen
2010-12-17 7:34 ` Jens Axboe [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=4D0B129B.3070500@fusionio.com \
--to=jaxboe@fusionio.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=lars.ellenberg@linbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mpatocka@redhat.com \
--cc=snitzer@redhat.com \
--cc=stable@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