From: Matthew Wilcox <willy@infradead.org>
To: "Qun-wei Lin (林群崴)" <Qun-wei.Lin@mediatek.com>
Cc: "ying.huang@intel.com" <ying.huang@intel.com>,
"Andrew Yang (楊智強)" <Andrew.Yang@mediatek.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"baohua@kernel.org" <baohua@kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
wsd_upstream <wsd_upstream@mediatek.com>,
"david@redhat.com" <david@redhat.com>,
"schatzberg.dan@gmail.com" <schatzberg.dan@gmail.com>,
"Chinwen Chang (張錦文)" <chinwen.chang@mediatek.com>,
"John Hsu (許永翰)" <John.Hsu@mediatek.com>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"kasong@tencent.com" <kasong@tencent.com>,
"Casper Li (李中榮)" <casper.li@mediatek.com>,
"chrisl@kernel.org" <chrisl@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"ryan.roberts@arm.com" <ryan.roberts@arm.com>
Subject: Re: [PATCH 0/2] Add BLK_FEAT_READ_SYNCHRONOUS and SWP_READ_SYNCHRONOUS_IO
Date: Sat, 12 Oct 2024 08:14:56 +0100 [thread overview]
Message-ID: <Zwoh8DrKgSD99xVQ@casper.infradead.org> (raw)
In-Reply-To: <17b30f253172cce94d1e2ec86d00e82eea077bde.camel@mediatek.com>
On Fri, Oct 11, 2024 at 09:08:10AM +0000, Qun-wei Lin (林群崴) wrote:
> The primary motivation for these new feature flags is to handle
> scenarios where we want read operations to be completed within the
> submit context, while write operations are handled in a different
> context.
>
> This does not necessarily imply that the write operations are slow;
> rather, it is about optimizing the handling of read and write
> operations based on their specific characteristics and requirements.
So why wouldn't we always want to do that instead of making it a
per-bdev flag?
prev parent reply other threads:[~2024-10-12 7:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-19 11:29 Qun-Wei Lin
2024-09-19 11:29 ` [PATCH 1/2] block: add BLK_FEAT_READ_SYNCHRONOUS feature for synchronous read Qun-Wei Lin
2024-09-19 11:29 ` [PATCH 2/2] mm, swap: introduce SWP_READ_SYNCHRONOUS_IO Qun-Wei Lin
2024-09-19 11:37 ` [PATCH 0/2] Add BLK_FEAT_READ_SYNCHRONOUS and SWP_READ_SYNCHRONOUS_IO Christoph Hellwig
2024-09-21 0:04 ` Chris Li
2024-09-27 10:14 ` Qun-wei Lin (林群崴)
2024-09-25 7:34 ` Huang, Ying
2024-10-11 9:08 ` Qun-wei Lin (林群崴)
2024-10-12 7:14 ` Matthew Wilcox [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=Zwoh8DrKgSD99xVQ@casper.infradead.org \
--to=willy@infradead.org \
--cc=Andrew.Yang@mediatek.com \
--cc=John.Hsu@mediatek.com \
--cc=Qun-wei.Lin@mediatek.com \
--cc=akpm@linux-foundation.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=axboe@kernel.dk \
--cc=baohua@kernel.org \
--cc=casper.li@mediatek.com \
--cc=chinwen.chang@mediatek.com \
--cc=chrisl@kernel.org \
--cc=david@redhat.com \
--cc=kasong@tencent.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=matthias.bgg@gmail.com \
--cc=ryan.roberts@arm.com \
--cc=schatzberg.dan@gmail.com \
--cc=viro@zeniv.linux.org.uk \
--cc=wsd_upstream@mediatek.com \
--cc=ying.huang@intel.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