On Thu, Aug 14, 2025 at 5:31 AM Yu Kuai <yukuai1@xxxxxxxxxxxxxxx> wrote: > > Hi, > > 在 2025/08/14 13:14, Teng Qin 写道: >> Moreover, the block layer documentation at >> Documentation/ABI/stable/sysfs-block >> still documents the legacy behavior of the io_poll sysfs file. This is >> confusing for users trying to figure out reason of the failed or >> unexpected behavior after writing to the file and seeing the dmesg, >> particularly because there are many articles on the Internet describing >> the legacy behavior. >> If the maintainers agree, I can help update these documentations. > > Feel free to update the documentations, AFAIK, there are some out of > date descriptions and it's welcome to fix them Thanks a lot for the information. Before writing anything, I just want to confirm there is indeed no more per-device control for polling behavior? Is io_uring and driver-specific features like nvme passthrough the only ways to go right now? For users who have legacy applications that could benefit from polling but still make traditional IO calls, would it still make sense to add a per-device override? I can think of some ways of adding a config for a specific device so it would tag all bio-s for that device as polling (if queue capable). But I'm not sure if that has been discussed before or maybe that was intentionally discouraged? Would love to hear from the maintainers for opinion. > > > Thanks, > Kuai >
