From: Bart Van Assche via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Bart Van Assche <bvanassche@acm.org>,
linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [PATCH 0/4] Reduce the time spent in interrupt context
Date: Thu, 28 May 2026 14:20:24 -0700 [thread overview]
Message-ID: <cover.1780003055.git.bvanassche@acm.org> (raw)
Hi Jaegeuk,
This patch series reduces the amount of time spent in interrupt context for
completing write bios. Please consider this patch series for the next merge
window.
Thanks,
Bart.
Bart Van Assche (4):
f2fs: Prepare for supporting delayed bio completion
f2fs: Rename f2fs_post_read_wq into f2fs_wq
f2fs: Split f2fs_write_end_io()
f2fs: Run f2fs_write_end_io() asynchronously
fs/f2fs/compress.c | 2 +-
fs/f2fs/data.c | 62 +++++++++++++++++++++++++++++++---------------
fs/f2fs/f2fs.h | 8 +++---
fs/f2fs/super.c | 13 +++++++---
fs/f2fs/sysfs.c | 2 ++
5 files changed, 59 insertions(+), 28 deletions(-)
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next reply other threads:[~2026-05-28 21:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 21:20 Bart Van Assche via Linux-f2fs-devel [this message]
2026-05-28 21:20 ` [f2fs-dev] [PATCH 1/4] f2fs: Prepare for supporting delayed bio completion Bart Van Assche via Linux-f2fs-devel
2026-05-28 21:20 ` [f2fs-dev] [PATCH 2/4] f2fs: Rename f2fs_post_read_wq into f2fs_wq Bart Van Assche via Linux-f2fs-devel
2026-05-28 21:20 ` [f2fs-dev] [PATCH 3/4] f2fs: Split f2fs_write_end_io() Bart Van Assche via Linux-f2fs-devel
2026-05-28 21:20 ` [f2fs-dev] [PATCH 4/4] f2fs: Run f2fs_write_end_io() asynchronously Bart Van Assche via Linux-f2fs-devel
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=cover.1780003055.git.bvanassche@acm.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=bvanassche@acm.org \
--cc=jaegeuk@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.