linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
To: Matthew Wilcox <willy@infradead.org>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	Jens Axboe <axboe@kernel.dk>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v2] block: Add bio_max_segs
Date: Fri, 26 Feb 2021 20:50:21 +0000	[thread overview]
Message-ID: <DM6PR04MB497224CEBD0261A620A47E35869D9@DM6PR04MB4972.namprd04.prod.outlook.com> (raw)
In-Reply-To: 20210226203819.GH2723601@casper.infradead.org

On 2/26/21 12:39, Matthew Wilcox wrote:
> This seems to have missed the merge window ;-(
>
> On Fri, Jan 29, 2021 at 04:38:57AM +0000, Matthew Wilcox (Oracle) wrote:
>> It's often inconvenient to use BIO_MAX_PAGES due to min() requiring the
>> sign to be the same.  Introduce bio_max_segs() and change BIO_MAX_PAGES to
>> be unsigned to make it easier for the users.
>>
>> Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
>> ---
>> v2:
>>  - Rename from bio_limit() to bio_max_segs()
>>  - Rebase on next-20210128
>>  - Use DIV_ROUND_UP in dm-log-writes.c
>>  - Use DIV_ROUND_UP in iomap/buffered-io.c
Looks good.

Reviewed-by: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>

  reply	other threads:[~2021-02-26 20:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-29  4:38 [PATCH v2] block: Add bio_max_segs Matthew Wilcox (Oracle)
2021-02-26 20:38 ` Matthew Wilcox
2021-02-26 20:50   ` Chaitanya Kulkarni [this message]
2021-02-26 22:50   ` Jens Axboe

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=DM6PR04MB497224CEBD0261A620A47E35869D9@DM6PR04MB4972.namprd04.prod.outlook.com \
    --to=chaitanya.kulkarni@wdc.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=willy@infradead.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).