|
|
Subscribe / Log in / New account

There's a better solution than falling back to buffered io

There's a better solution than falling back to buffered io

Posted Nov 12, 2025 19:28 UTC (Wed) by Paf (subscriber, #91811)
In reply to: There's a better solution than falling back to buffered io by nickodell
Parent article: The intersection of unstable pages and direct I/O

At least for small pages, much of the cost of using the page cache is actually in setup, insertion, and removal from the cache, *not* in memory allocation or data copying. Depending on the use case and hardware, simple bounce buffers can be *much* faster. And they can be done in parallel across many threads without conflicting on the tree locking for the page cache. (Even a read is a tree insert unless the data is already present.)

But this becomes proportionally less true with large folios though, probably to the point of not really true for larger sizes, since the overhead is spread over much more data.


to post comments

There's a better solution than falling back to buffered io

Posted Nov 12, 2025 19:36 UTC (Wed) by koverstreet (✭ supporter ✭, #4296) [Link]

IOPs keep going up, though. Forcing everything through the buffered IO paths is just crippling.


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds