[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZwjtSe8zL3WO32h5@infradead.org>
Date: Fri, 11 Oct 2024 02:18:01 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Qun-Wei Lin <qun-wei.lin@...iatek.com>
Cc: Jens Axboe <axboe@...nel.dk>, Minchan Kim <minchan@...nel.org>,
Sergey Senozhatsky <senozhatsky@...omium.org>,
Vishal Verma <vishal.l.verma@...el.com>,
Dan Williams <dan.j.williams@...el.com>,
Dave Jiang <dave.jiang@...el.com>, Ira Weiny <ira.weiny@...el.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Matthias Brugger <matthias.bgg@...il.com>,
AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>,
"Huang, Ying" <ying.huang@...el.com>, Chris Li <chrisl@...nel.org>,
Ryan Roberts <ryan.roberts@....com>,
David Hildenbrand <david@...hat.com>,
Kairui Song <kasong@...cent.com>,
"Matthew Wilcox (Oracle)" <willy@...radead.org>,
Dan Schatzberg <schatzberg.dan@...il.com>,
Barry Song <baohua@...nel.org>, linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org, nvdimm@...ts.linux.dev,
linux-mm@...ck.org, linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org,
Casper Li <casper.li@...iatek.com>,
Chinwen Chang <chinwen.chang@...iatek.com>,
Andrew Yang <andrew.yang@...iatek.com>,
John Hsu <john.hsu@...iatek.com>, wsd_upstream@...iatek.com
Subject: Re: [PATCH] mm: Split BLK_FEAT_SYNCHRONOUS and SWP_SYNCHRONOUS_IO
into separate read and write flags
On Fri, Oct 11, 2024 at 05:11:33PM +0800, Qun-Wei Lin wrote:
> This patch splits the BLK_FEAT_SYNCHRONOUS feature flag into two
> separate flags: BLK_FEAT_READ_SYNCHRONOUS and
> BLK_FEAT_WRITE_SYNCHRONOUS. Similarly, the SWP_SYNCHRONOUS_IO flag is
> split into SWP_READ_SYNCHRONOUS_IO and SWP_WRITE_SYNCHRONOUS_IO.
>
> These changes are motivated by the need to better accommodate certain
> swap devices that support synchronous read operations but asynchronous write
> operations.
>
> The existing BLK_FEAT_SYNCHRONOUS and SWP_SYNCHRONOUS_IO flags are not
> sufficient for these devices, as they enforce synchronous behavior for
> both read and write operations.
You're still failing to provide a user. Without that it is dead in
the water from the very beginning.
Powered by blists - more mailing lists