fuse: optimize over-io-uring request expiration check

Browse source

Currently, when checking whether a request has timed out, we check
fpq processing, but fuse-over-io-uring has one fpq per core and 256
entries in the processing table. For systems where there are a
large number of cores, this may be too much overhead.

Instead of checking the fpq processing list, check ent_w_req_queue
and ent_in_userspace.

Signed-off-by: Joanne Koong <joannelkoong@gmail.com>
Reviewed-by: Bernd Schubert <bernd@bsbernd.com>
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>

...

This commit is contained in:

Joanne Koong 2025-02-03 11:30:22 -08:00 • committed by Miklos Szeredi

parent 03a3617f92

commit 4fea593e62

3 changed files with 22 additions and 7 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

2

fs/fuse/dev.c

View file

26

fs/fuse/dev_uring.c

View file

1

fs/fuse/fuse_dev_i.h

View file