Linux XFS filesystem development
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: "zhaoyifan (H)" <zhaoyifan28@huawei.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Gao Xiang <hsiangkao@linux.alibaba.com>,
	linux-erofs@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	yekelu1@huawei.com, jingrui@huawei.com, zhukeqian1@huawei.com,
	Ritesh Harjani <ritesh.list@gmail.com>,
	"Darrick J. Wong" <djwong@kernel.org>,
	linux-xfs@vger.kernel.org, Joanne Koong <joannelkoong@gmail.com>
Subject: Re: don't merge bios over iomap boundaries, was: Re: [PATCH] erofs: prevent buffered read bio merges across device chunks
Date: Thu, 18 Jun 2026 02:00:59 -0700	[thread overview]
Message-ID: <ajOzy2NPD2GlXcNt@infradead.org> (raw)
In-Reply-To: <fbc281ab-09ba-4e3a-90cd-2babc708fdc4@huawei.com>

On Thu, Jun 18, 2026 at 03:16:03PM +0800, zhaoyifan (H) wrote:
> Hi Christoph,
> 
> 
> This patch works well under my workload (at least correctness-wise). Thanks.

Thanks.

Gao, do we need any erofs updates to go along with this to not regress
behavior where it would have merged before?


  reply	other threads:[~2026-06-18  9:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260612033244.993507-1-zhaoyifan28@huawei.com>
     [not found] ` <58bef9af-0926-4948-b917-e38c3793f596@linux.alibaba.com>
2026-06-12  6:25   ` don't merge bios over iomap boundaries, was: Re: [PATCH] erofs: prevent buffered read bio merges across device chunks Christoph Hellwig
2026-06-12  6:54     ` Gao Xiang
2026-06-12  7:10       ` Christoph Hellwig
2026-06-12  7:19         ` Gao Xiang
2026-06-12  7:35           ` Gao Xiang
2026-06-12  8:04             ` Christoph Hellwig
2026-06-12  8:01           ` Christoph Hellwig
2026-06-18  7:16     ` zhaoyifan (H)
2026-06-18  9:00       ` Christoph Hellwig [this message]
2026-06-18 10:14         ` Gao Xiang
2026-06-18 10:27           ` Christoph Hellwig
2026-06-18 10:53             ` Gao Xiang

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=ajOzy2NPD2GlXcNt@infradead.org \
    --to=hch@infradead.org \
    --cc=djwong@kernel.org \
    --cc=hsiangkao@linux.alibaba.com \
    --cc=jingrui@huawei.com \
    --cc=joannelkoong@gmail.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=ritesh.list@gmail.com \
    --cc=yekelu1@huawei.com \
    --cc=zhaoyifan28@huawei.com \
    --cc=zhukeqian1@huawei.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