diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2022-09-02 16:37:01 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2022-09-02 16:37:01 -0700 |
commit | cec53f4c8df0b3f45796127a31c10b86ec125f55 (patch) | |
tree | f1765cb76b1115c0b0ad58c52003b0db2024686a /drivers/atm/idt77105.h | |
parent | 1551f8f21e007e608fff00cf27caac8504283b43 (diff) | |
parent | 916d72c10a4ca80ea51f1421e774cb765b53f28f (diff) | |
download | linux-cec53f4c8df0b3f45796127a31c10b86ec125f55.tar.bz2 |
Merge tag 'io_uring-6.0-2022-09-02' of git://git.kernel.dk/linux-block
Pull io_uring fixes from Jens Axboe:
- A single fix for over-eager retries for networking (Pavel)
- Revert the notification slot support for zerocopy sends.
It turns out that even after more than a year or development and
testing, there's not full agreement on whether just using plain
ordered notifications is Good Enough to avoid the complexity of using
the notifications slots. Because of that, we decided that it's best
left to a future final decision.
We can always bring back this feature, but we can't really change it
or remove it once we've released 6.0 with it enabled. The reverts
leave the usual CQE notifications as the primary interface for
knowing when data was sent, and when it was acked. (Pavel)
* tag 'io_uring-6.0-2022-09-02' of git://git.kernel.dk/linux-block:
selftests/net: return back io_uring zc send tests
io_uring/net: simplify zerocopy send user API
io_uring/notif: remove notif registration
Revert "io_uring: rename IORING_OP_FILES_UPDATE"
Revert "io_uring: add zc notification flush requests"
selftests/net: temporarily disable io_uring zc test
io_uring/net: fix overexcessive retries
Diffstat (limited to 'drivers/atm/idt77105.h')
0 files changed, 0 insertions, 0 deletions