[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <042d3631-e3ab-437a-b628-4004ca3ddb45@redhat.com>
Date: Fri, 20 Dec 2024 16:03:44 +0100
From: David Hildenbrand <david@...hat.com>
To: "Kirill A. Shutemov" <kirill@...temov.name>, Jens Axboe <axboe@...nel.dk>
Cc: linux-mm@...ck.org, linux-fsdevel@...r.kernel.org, hannes@...xchg.org,
clm@...a.com, linux-kernel@...r.kernel.org, willy@...radead.org,
bfoster@...hat.com, Vlastimil Babka <vbabka@...e.cz>
Subject: Re: [PATCH 04/11] mm: add PG_dropbehind folio flag
On 20.12.24 12:08, Kirill A. Shutemov wrote:
> On Fri, Dec 13, 2024 at 08:55:18AM -0700, Jens Axboe wrote:
>> Add a folio flag that file IO can use to indicate that the cached IO
>> being done should be dropped from the page cache upon completion.
>>
>> Signed-off-by: Jens Axboe <axboe@...nel.dk>
>
> Reviewed-by: Kirill A. Shutemov <kirill.shutemov@...ux.intel.com>
>
> + David, Vlastimil.
>
> I think we should consider converting existing folio_set_reclaim() /
> SetPageReclaim() users to the new flag. From a quick scan, all of them
> would benefit from dropping the page after writeback is complete instead
> of leaving the folio on the LRU.
I wonder of there are some use cases where we write a lot of data to
then only consume it read-only from that point on (databases? fancy AI
stuff? no idea :) ).
--
Cheers,
David / dhildenb
Powered by blists - more mailing lists