mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Bart Van Assche <bvanassche@acm.org>,
	Changheun Lee <nanich.lee@samsung.com>,
	yi.zhang@redhat.com, ming.lei@redhat.com, bgoncalv@redhat.com,
	hch@lst.de, jaegeuk@kernel.org, linux-block@vger.kernel.org,
	linux-kernel@vger.kernel.org, patchwork-bot@kernel.org
Subject: Re: [PATCH v9] bio: limit bio max size
Date: Mon, 3 May 2021 08:59:41 -0600	[thread overview]
Message-ID: <c48d45cc-9c4f-0b6c-51d0-3044e7cdf7f5@kernel.dk> (raw)
In-Reply-To: <72a0b4e7-a374-97fb-ae73-ed24f719da98@acm.org>

On 5/3/21 8:54 AM, Bart Van Assche wrote:
> On 5/3/21 2:52 AM, Changheun Lee wrote:
>>  struct queue_limits {
>> +	unsigned int		bio_max_bytes;
>> +
>>  	enum blk_bounce		bounce;
>>  	unsigned long		seg_boundary_mask;
>>  	unsigned long		virt_boundary_mask;
> 
> On April 23 Damien Le Moal posted the following comment about the
> bio_max_bytes member: "Please move this below in the structure together
> with all other fields that are unsigned int too." Making that change
> sounds like a good idea to me.

Why? It's next to an enum, so the patch (as it stands) actually fills a
hole in the struct. Moving it would be a mistake and waste more space.

If anything, we should move the bounce member below virt_boundary_mask,
but since this one fills a hole, that's better left as a separate patch.

-- 
Jens Axboe


  reply	other threads:[~2021-05-03 14:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20210503101008epcas1p25d6b727dafcf9ff24db6aa41a3f611fa@epcas1p2.samsung.com>
2021-05-03  9:52 ` Changheun Lee
2021-05-03 14:54   ` Bart Van Assche
2021-05-03 14:59     ` Jens Axboe [this message]
2021-05-03 16:33   ` Bart Van Assche
2021-05-03 17:42   ` 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=c48d45cc-9c4f-0b6c-51d0-3044e7cdf7f5@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=bgoncalv@redhat.com \
    --cc=bvanassche@acm.org \
    --cc=hch@lst.de \
    --cc=jaegeuk@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=nanich.lee@samsung.com \
    --cc=patchwork-bot@kernel.org \
    --cc=yi.zhang@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

all inboxes | Powered by JetHome®