linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: Christian Brauner <brauner@kernel.org>,
	john.g.garry@oracle.com, hch@lst.de, ritesh.list@gmail.com,
	linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
	linux-mm@kvack.org, linux-block@vger.kernel.org,
	gost.dev@samsung.com, p.raghav@samsung.com, da.gomez@samsung.com,
	kernel@pankajraghav.com, akpm@linux-foundation.org, hare@suse.de,
	willy@infradead.org, dave@stgolabs.net, david@fromorbit.com,
	djwong@kernel.org, kbusch@kernel.org
Subject: Re: [PATCH v3 0/8] enable bs > ps for block devices
Date: Mon, 24 Feb 2025 11:45:19 +0100	[thread overview]
Message-ID: <20250224-sehtest-messbar-784a08cdaf75@brauner> (raw)
In-Reply-To: <20250221223823.1680616-1-mcgrof@kernel.org>

On Fri, 21 Feb 2025 14:38:15 -0800, Luis Chamberlain wrote:
> Christian, Andrew,
> 
> This v3 series addresses the feedback from the v2 series [0]. The only
> patch which was mofified was the patch titled "fs/mpage: use blocks_per_folio
> instead of blocks_per_page". The motivation for this series is to mainly
> start supporting block devices with logical block sizes larger than 4k,
> we do this by addressing buffer-head support required for the block
> device cache.
> 
> [...]

Applied to the vfs-6.15.pagesize branch of the vfs/vfs.git tree.
Patches in the vfs-6.15.pagesize branch should appear in linux-next soon.

Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.

It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.

Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs-6.15.pagesize

[1/8] fs/buffer: simplify block_read_full_folio() with bh_offset()
      https://git.kernel.org/vfs/vfs/c/753aadebf2e3
[2/8] fs/buffer: remove batching from async read
      https://git.kernel.org/vfs/vfs/c/b72e591f74de
[3/8] fs/mpage: avoid negative shift for large blocksize
      https://git.kernel.org/vfs/vfs/c/86c60efd7c0e
[4/8] fs/mpage: use blocks_per_folio instead of blocks_per_page
      https://git.kernel.org/vfs/vfs/c/8b45a4f4133d
[5/8] fs/buffer fs/mpage: remove large folio restriction
      https://git.kernel.org/vfs/vfs/c/e59e97d42b05
[6/8] block/bdev: enable large folio support for large logical block sizes
      https://git.kernel.org/vfs/vfs/c/3c20917120ce
[7/8] block/bdev: lift block size restrictions to 64k
      https://git.kernel.org/vfs/vfs/c/47dd67532303
[8/8] bdev: use bdev_io_min() for statx block size
      https://git.kernel.org/vfs/vfs/c/425fbcd62d2e


      parent reply	other threads:[~2025-02-24 10:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-21 22:38 Luis Chamberlain
2025-02-21 22:38 ` [PATCH v3 1/8] fs/buffer: simplify block_read_full_folio() with bh_offset() Luis Chamberlain
2025-02-21 22:38 ` [PATCH v3 2/8] fs/buffer: remove batching from async read Luis Chamberlain
2025-02-21 22:38 ` [PATCH v3 3/8] fs/mpage: avoid negative shift for large blocksize Luis Chamberlain
2025-02-21 22:38 ` [PATCH v3 4/8] fs/mpage: use blocks_per_folio instead of blocks_per_page Luis Chamberlain
2025-02-24  7:44   ` Hannes Reinecke
2025-02-21 22:38 ` [PATCH v3 5/8] fs/buffer fs/mpage: remove large folio restriction Luis Chamberlain
2025-02-21 22:38 ` [PATCH v3 6/8] block/bdev: enable large folio support for large logical block sizes Luis Chamberlain
2025-02-21 22:38 ` [PATCH v3 7/8] block/bdev: lift block size restrictions to 64k Luis Chamberlain
2025-02-21 22:38 ` [PATCH v3 8/8] bdev: use bdev_io_min() for statx block size Luis Chamberlain
2025-02-24 10:45 ` Christian Brauner [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=20250224-sehtest-messbar-784a08cdaf75@brauner \
    --to=brauner@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=da.gomez@samsung.com \
    --cc=dave@stgolabs.net \
    --cc=david@fromorbit.com \
    --cc=djwong@kernel.org \
    --cc=gost.dev@samsung.com \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=john.g.garry@oracle.com \
    --cc=kbusch@kernel.org \
    --cc=kernel@pankajraghav.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=p.raghav@samsung.com \
    --cc=ritesh.list@gmail.com \
    --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