All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ritesh Harjani (IBM)" <ritesh.list@gmail.com>
To: linux-xfs@vger.kernel.org
Cc: linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	Matthew Wilcox <willy@infradead.org>,
	"Darrick J . Wong" <djwong@kernel.org>,
	Ojaswin Mujoo <ojaswin@linux.ibm.com>,
	Ritesh Harjani <ritesh.list@gmail.com>, Jan Kara <jack@suse.cz>
Subject: [PATCHv2 0/2] iomap: Optimize read_folio
Date: Tue,  7 May 2024 14:25:41 +0530	[thread overview]
Message-ID: <cover.1715067055.git.ritesh.list@gmail.com> (raw)

Hello,

Please find these two patches which were identified while working on ext2
buffered-io conversion to iomap. One of them is a bug fix and the other one
optimizes the read_folio path. More details can be found in individual
commit messages.

[v1]: https://lore.kernel.org/all/cover.1714046808.git.ritesh.list@gmail.com/

Ritesh Harjani (IBM) (2):
  iomap: Fix iomap_adjust_read_range for plen calculation
  iomap: Optimize iomap_read_folio

 fs/iomap/buffered-io.c | 23 +++++++++++++++++++++--
 1 file changed, 21 insertions(+), 2 deletions(-)

--
2.44.0


             reply	other threads:[~2024-05-07  8:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-07  8:55 Ritesh Harjani (IBM) [this message]
2024-05-07  8:55 ` [PATCHv2 1/2] iomap: Fix iomap_adjust_read_range for plen calculation Ritesh Harjani (IBM)
2024-05-09 10:33   ` Jan Kara
2024-06-05 15:29   ` (subset) " Christian Brauner
2024-05-07  8:55 ` [PATCHv2 2/2] iomap: Optimize iomap_read_folio Ritesh Harjani (IBM)
2024-05-07 21:11   ` Darrick J. Wong
2024-05-09  4:55   ` Christoph Hellwig
2024-05-09 10:40   ` Jan Kara
2024-06-05 15:29   ` (subset) " Christian Brauner
2024-06-04  0:32 ` [PATCHv2 0/2] iomap: Optimize read_folio Ritesh Harjani
2024-06-04  4:11   ` Christoph Hellwig

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.1715067055.git.ritesh.list@gmail.com \
    --to=ritesh.list@gmail.com \
    --cc=djwong@kernel.org \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=ojaswin@linux.ibm.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 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.