All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Hannes Reinecke <hare@suse.de>
Cc: Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org, Luis Chamberlain <mcgrof@kernel.org>,
	Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCH 4/5] brd: limit maximal block size to 32M
Date: Mon, 6 Mar 2023 17:40:04 +0000	[thread overview]
Message-ID: <ZAYldLT52jAc82Xj@casper.infradead.org> (raw)
In-Reply-To: <20230306120127.21375-5-hare@suse.de>

On Mon, Mar 06, 2023 at 01:01:26PM +0100, Hannes Reinecke wrote:
> Use an arbitrary limit of 32M for the maximal blocksize so as not
> to overflow the page cache.

The page allocator tops out at MAX_ORDER (generally 4MB), so that might
be a better limit.  Also, this has nothing to do with the page cache,
right?

  reply	other threads:[~2023-03-06 17:41 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20230307114200eucas1p296a60514feb40c4a08f380cc28aeeb51@eucas1p2.samsung.com>
2023-03-06 12:01 ` [PATCH 0/5] brd: Allow to change block sizes Hannes Reinecke
2023-03-06 12:01   ` [PATCH 1/5] brd: convert to folios Hannes Reinecke
2023-03-06 16:04     ` kernel test robot
2023-03-06 17:37     ` Matthew Wilcox
2023-03-07  6:55       ` Hannes Reinecke
2023-03-07  7:30         ` Matthew Wilcox
2023-03-09  3:28           ` Luis Chamberlain
     [not found]           ` <a4489f7b-912c-e68f-4a4c-c14d96026bd6@suse.de>
2023-03-21 15:00             ` Matthew Wilcox
2023-03-21 15:26               ` Hannes Reinecke
2023-03-09  2:29     ` Luis Chamberlain
2023-03-06 12:01   ` [PATCH 2/5] brd: abstract page_size conventions Hannes Reinecke
2023-03-06 12:01   ` [PATCH 3/5] brd: make sector size configurable Hannes Reinecke
2023-03-09  3:12     ` Luis Chamberlain
2023-03-20 22:52       ` Luis Chamberlain
2023-03-20 23:40         ` Martin K. Petersen
2023-03-21  0:14           ` Luis Chamberlain
2023-03-06 12:01   ` [PATCH 4/5] brd: limit maximal block size to 32M Hannes Reinecke
2023-03-06 17:40     ` Matthew Wilcox [this message]
2023-03-07  6:56       ` Hannes Reinecke
2023-03-06 18:01     ` Keith Busch
2023-03-07  6:57       ` Hannes Reinecke
2023-03-06 12:01   ` [PATCH 5/5] brd: make logical sector size configurable Hannes Reinecke
2023-03-07  9:01     ` Pankaj Raghav
2023-03-07 11:06       ` Hannes Reinecke
2023-05-17  9:31     ` Pankaj Raghav
2023-03-07 11:33   ` [PATCH 0/5] brd: Allow to change block sizes Pankaj Raghav

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=ZAYldLT52jAc82Xj@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=axboe@kernel.dk \
    --cc=hare@suse.de \
    --cc=kbusch@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=mcgrof@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.