Linux-mm Archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: Christoph Hellwig <hch@infradead.org>,
	Luis Chamberlain <mcgrof@kernel.org>,
	akpm@linux-foundation.org, djwong@kernel.org, brauner@kernel.org,
	david@fromorbit.com, chandan.babu@oracle.com, hare@suse.de,
	ritesh.list@gmail.com, john.g.garry@oracle.com, ziy@nvidia.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,
	kernel@pankajraghav.com
Subject: Re: [PATCH v5 07/11] iomap: fix iomap_dio_zero() for fs bs > system page size
Date: Wed, 8 May 2024 04:36:40 -0700	[thread overview]
Message-ID: <ZjtjyM60ebrJfAmM@infradead.org> (raw)
In-Reply-To: <Zjr-lf2tJAmwLzzu@casper.infradead.org>

On Wed, May 08, 2024 at 05:24:53AM +0100, Matthew Wilcox wrote:
> On Tue, May 07, 2024 at 09:13:17AM -0700, Christoph Hellwig wrote:
> > On Tue, May 07, 2024 at 05:11:58PM +0100, Matthew Wilcox wrote:
> > > > 	__bio_add_page(bio, page, len, 0);
> > > 
> > > no?  len can be > PAGE_SIZE.
> > 
> > Yes. So what?
> 
> the zero_page is only PAGE_SIZE bytes long.  so you'd be writing
> from the page that's after the zero page, whatever contents that has.

Except that the whole point of the exercise is to use the huge folio
so that we don't run past the end of the zero page.  Yes, if we use
ZERO_PAGE we need to chunk things up and use bio_add_page instead
bio_page, check the return value and potentially deal with multiple
bios.  I'd rather avoid that, though.



  parent reply	other threads:[~2024-05-08 11:36 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-03  9:53 [PATCH v5 00/11] enable bs > ps in XFS Luis Chamberlain
2024-05-03  9:53 ` [PATCH v5 01/11] readahead: rework loop in page_cache_ra_unbounded() Luis Chamberlain
2024-05-03  9:53 ` [PATCH v5 02/11] fs: Allow fine-grained control of folio sizes Luis Chamberlain
2024-05-03  9:53 ` [PATCH v5 03/11] filemap: allocate mapping_min_order folios in the page cache Luis Chamberlain
2024-05-03  9:53 ` [PATCH v5 04/11] readahead: allocate folios with mapping_min_order in readahead Luis Chamberlain
2024-05-03 14:32   ` Hannes Reinecke
2024-05-03  9:53 ` [PATCH v5 05/11] mm: split a folio in minimum folio order chunks Luis Chamberlain
2024-05-03 14:53   ` Zi Yan
2024-05-15 15:32   ` Matthew Wilcox
2024-05-16 14:56     ` Pankaj Raghav (Samsung)
2024-05-03  9:53 ` [PATCH v5 06/11] filemap: cap PTE range to be created to allowed zero fill in folio_map_range() Luis Chamberlain
2024-05-03  9:53 ` [PATCH v5 07/11] iomap: fix iomap_dio_zero() for fs bs > system page size Luis Chamberlain
2024-05-07 14:58   ` [RFC] iomap: use huge zero folio in iomap_dio_zero Pankaj Raghav (Samsung)
2024-05-07 15:11     ` Zi Yan
2024-05-07 16:11     ` Christoph Hellwig
2024-05-08 11:39       ` Pankaj Raghav (Samsung)
2024-05-08 11:43         ` Christoph Hellwig
2024-05-09 12:31           ` Pankaj Raghav (Samsung)
2024-05-09 12:46             ` Christoph Hellwig
2024-05-09 12:55               ` Pankaj Raghav (Samsung)
2024-05-09 12:58                 ` Christoph Hellwig
2024-05-09 14:32                   ` Darrick J. Wong
2024-05-09 15:05                     ` Christoph Hellwig
2024-05-09 15:08                       ` Darrick J. Wong
2024-05-09 15:09                         ` Christoph Hellwig
2024-05-15  0:50     ` Matthew Wilcox
2024-05-15  2:34       ` Keith Busch
2024-05-15  4:04         ` Matthew Wilcox
2024-05-15 15:59           ` Pankaj Raghav (Samsung)
2024-05-15 18:03             ` Matthew Wilcox
2024-05-16 15:02               ` Pankaj Raghav (Samsung)
2024-05-17 12:36                 ` Hannes Reinecke
2024-05-17 12:56                   ` Hannes Reinecke
2024-05-17 13:30                   ` Matthew Wilcox
2024-05-15 11:48       ` Christoph Hellwig
2024-05-07 16:00   ` [PATCH v5 07/11] iomap: fix iomap_dio_zero() for fs bs > system page size Matthew Wilcox
2024-05-07 16:10     ` Christoph Hellwig
2024-05-07 16:11       ` Matthew Wilcox
2024-05-07 16:13         ` Christoph Hellwig
2024-05-08  4:24           ` Matthew Wilcox
2024-05-08 11:22             ` Pankaj Raghav (Samsung)
2024-05-08 11:36             ` Christoph Hellwig [this message]
2024-05-08 11:20     ` Pankaj Raghav (Samsung)
2024-05-03  9:53 ` [PATCH v5 08/11] xfs: use kvmalloc for xattr buffers Luis Chamberlain
2024-05-03  9:53 ` [PATCH v5 09/11] xfs: expose block size in stat Luis Chamberlain
2024-05-03  9:53 ` [PATCH v5 10/11] xfs: make the calculation generic in xfs_sb_validate_fsb_count() Luis Chamberlain
2024-05-07  8:40   ` John Garry
2024-05-07 21:13     ` Darrick J. Wong
2024-05-08 11:28       ` Pankaj Raghav (Samsung)
2024-05-03  9:53 ` [PATCH v5 11/11] xfs: enable block size larger than page size support Luis Chamberlain
2024-05-07  0:05   ` Dave Chinner

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=ZjtjyM60ebrJfAmM@infradead.org \
    --to=hch@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=brauner@kernel.org \
    --cc=chandan.babu@oracle.com \
    --cc=david@fromorbit.com \
    --cc=djwong@kernel.org \
    --cc=gost.dev@samsung.com \
    --cc=hare@suse.de \
    --cc=john.g.garry@oracle.com \
    --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 \
    --cc=ziy@nvidia.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).