Reiserfs development archive or lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Matthew Wilcox <willy@infradead.org>
Cc: reiserfs-devel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	Jan Kara <jack@suse.cz>
Subject: Re: [PATCH] reiserfs: Convert to writepages
Date: Fri, 12 Apr 2024 14:38:48 +0200	[thread overview]
Message-ID: <20240412123848.mv5y56uuz4tjdyaz@quack3> (raw)
In-Reply-To: <ZhgnMsJ9AGAkgFXT@casper.infradead.org>

On Thu 11-04-24 19:08:50, Matthew Wilcox wrote:
> On Tue, Mar 05, 2024 at 06:53:08PM +0000, Matthew Wilcox wrote:
> > On Tue, Mar 05, 2024 at 06:52:05PM +0000, Matthew Wilcox (Oracle) wrote:
> > > Use buffer_migrate_folio to handle folio migration instead of writing
> > > out dirty pages and reading them back in again.  Use writepages to write
> > > out folios more efficiently.  We now only do that wait_on_write_block
> > > check once per call to writepages instead of once per page.  It would be
> > > possible to do one transaction per writeback run, but that's a bit of a
> > > big change to do to this old filesystem, so leave it as one transaction
> > > per folio (and leave reiserfs supporting only one page per folio).
> > > 
> > > Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
> 
> This patch is not yet in linux-next.  Do I need to do anything to
> make that happen?

Hum, usually Andrew picks these up but he was not on CC this time. Queued
into my tree.

								Honza
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

      reply	other threads:[~2024-04-12 12:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240305185208.1200166-1-willy@infradead.org>
2024-03-05 18:53 ` [PATCH] reiserfs: Convert to writepages Matthew Wilcox
2024-04-11 18:08   ` Matthew Wilcox
2024-04-12 12:38     ` Jan Kara [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=20240412123848.mv5y56uuz4tjdyaz@quack3 \
    --to=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=reiserfs-devel@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 read-only IMAP folder(s) and NNTP newsgroup(s).