On Mon, Dec 09, 2024 at 01:51:32PM +0100, Christoph Hellwig wrote: > On Thu, Dec 05, 2024 at 05:52:58PM -0800, Keith Busch wrote: > > > > Not mixing write hints usage with write streams. This effectively > > abandons any attempts to use the existing fcntl API for use with > > filesystems in this series. > > That's not true as far as I can tell given that this is basically the > architecture from my previous posting. The block code still maps the > rw hints into write streams, and file systems can do exactly the same. > You just need to talk to the fs maintainers and convince them it's a > good thing for their particular file system. Especially for simple > file systems that task should not be too hard, even if they might want > to set a stream or two aside for fs usage. Similarly a file system > can implement the stream based API. Sorry for my confusing message here. I meant *this series* doesn't attempt to use streams with filesystems (I wasn't considering raw block in the same catagory as a traditional filesystems). I am not abandoning follow on efforst to make use of these elsewhere. I just don't want the open topics to distract from the less controversial parts, and this series doesn't prevent or harm future innovations there, so I think we're pretty well aligned up to this point.
