On 4/19/23 16:42, Bernd Schubert wrote:
On 4/19/23 13:19, Ming Lei wrote:
On Wed, Apr 19, 2023 at 09:56:43AM +0000, Bernd Schubert wrote:
On 4/19/23 03:51, Ming Lei wrote:
On Tue, Apr 18, 2023 at 07:38:03PM +0000, Bernd Schubert wrote:
On 3/30/23 13:36, Ming Lei wrote:
[...]
V6:
- re-design fused command, and make it more generic, moving sharing buffer
as one plugin of fused command, so in future we can implement more plugins
- document potential other use cases of fused command
- drop support for builtin secondary sqe in SQE128, so all secondary
requests has standalone SQE
- make fused command as one feature
- cleanup & improve naming
Hi Ming, et al.,
I started to wonder if fused SQE could be extended to combine multiple
syscalls, for example open/read/close. Which would be another solution
for the readfile syscall Miklos had proposed some time ago.
https://lore.kernel.org/lkml/CAJfpegusi8BjWFzEi05926d4RsEQvPnRW-w7My=ibBHQ8NgCuw@xxxxxxxxxxxxxx/
If fused SQEs could be extended, I think it would be quite helpful for
many other patterns. Another similar examples would open/write/close,
but ideal would be also to allow to have it more complex like
"open/write/sync_file_range/close" - open/write/close might be the
fastest and could possibly return before sync_file_range. Use case for
the latter would be a file server that wants to give notifications to
client when pages have been written out.
The above pattern needn't fused command, and it can be done by plain
SQEs chain, follows the usage:
1) suppose you get one command from /dev/fuse, then FUSE daemon
needs to handle the command as open/write/sync/close
2) get sqe1, prepare it for open syscall, mark it as IOSQE_IO_LINK;
3) get sqe2, prepare it for write syscall, mark it as IOSQE_IO_LINK;
4) get sqe3, prepare it for sync file range syscall, mark it as IOSQE_IO_LINK;
5) get sqe4, prepare it for close syscall
6) io_uring_enter(); //for submit and get events
Oh, I was not aware that IOSQE_IO_LINK could pass the result of open
down to the others. Hmm, the example I find for open is
io_uring_prep_openat_direct in test_open_fixed(). It probably gets off
topic here, but one needs to have ring prepared with
io_uring_register_files_sparse, then manually manages available indexes
and can then link commands? Interesting!
Yeah, see test/fixed-reuse.c of liburing
Then all the four OPs are done one by one by io_uring internal
machinery, and you can choose to get successful CQE for each OP.
Is the above what you want to do?
The fused command proposal is actually for zero copy(but not limited to zc).
Yeah, I had just thought that IORING_OP_FUSED_CMD could be modified to
support generic passing, as it kind of hands data (buffers) from one sqe
to the other. I.e. instead of buffers it would have passed the fd, but
if this is already possible - no need to make IORING_OP_FUSED_CMD more
complex.man
The way of passing FD introduces other cost, read op running into async,
and adding it into global table, which introduces runtime cost.
Hmm, question from my side is why it needs to be in the global table,
when it could be just passed to the linked or fused sqe?
Because for every such type of state you need to write custom code,
it's not scalable, not to say that it usually can't be kept to a
specific operation and leaks into generic paths / other requests.
Some may want to pass a file or a buffer, there might be a need
to pass a result in some specific way (e.g. nr = recv(); send(nr)),
and the list continues...
I tried adding BPF in the middle ~2y ago, but it was no
different in perf than returning to the userspace, and gets
worse with higher submission batching. Maybe I need to test
it again.
That is the reason why fused command is designed in the following way:
- link can be avoided, so OPs needn't to be run in async
- no need to add buffer into global table
Cause it is really in fast io path.
--
Pavel Begunkov
