Forum | Documentation | Website | Blog

Skip to content
Snippets Groups Projects
  1. Feb 09, 2024
    • Stefan Roesch's avatar
      io-uring: add sqpoll support for napi busy poll · ff183d42
      Stefan Roesch authored
      
      This adds the sqpoll support to the io-uring napi.
      
      Signed-off-by: default avatarStefan Roesch <shr@devkernel.io>
      Suggested-by: default avatarOlivier Langlois <olivier@trillion01.com>
      Link: https://lore.kernel.org/r/20230608163839.2891748-6-shr@devkernel.io
      
      
      Signed-off-by: default avatarJens Axboe <axboe@kernel.dk>
      ff183d42
    • Stefan Roesch's avatar
      io-uring: add napi busy poll support · 8d0c12a8
      Stefan Roesch authored
      
      This adds the napi busy polling support in io_uring.c. It adds a new
      napi_list to the io_ring_ctx structure. This list contains the list of
      napi_id's that are currently enabled for busy polling. The list is
      synchronized by the new napi_lock spin lock. The current default napi
      busy polling time is stored in napi_busy_poll_to. If napi busy polling
      is not enabled, the value is 0.
      
      In addition there is also a hash table. The hash table store the napi
      id and the pointer to the above list nodes. The hash table is used to
      speed up the lookup to the list elements. The hash table is synchronized
      with rcu.
      
      The NAPI_TIMEOUT is stored as a timeout to make sure that the time a
      napi entry is stored in the napi list is limited.
      
      The busy poll timeout is also stored as part of the io_wait_queue. This
      is necessary as for sq polling the poll interval needs to be adjusted
      and the napi callback allows only to pass in one value.
      
      This has been tested with two simple programs from the liburing library
      repository: the napi client and the napi server program. The client
      sends a request, which has a timestamp in its payload and the server
      replies with the same payload. The client calculates the roundtrip time
      and stores it to calculate the results.
      
      The client is running on host1 and the server is running on host 2 (in
      the same rack). The measured times below are roundtrip times. They are
      average times over 5 runs each. Each run measures 1 million roundtrips.
      
                         no rx coal          rx coal: frames=88,usecs=33
      Default              57us                    56us
      
      client_poll=100us    47us                    46us
      
      server_poll=100us    51us                    46us
      
      client_poll=100us+   40us                    40us
      server_poll=100us
      
      client_poll=100us+   41us                    39us
      server_poll=100us+
      prefer napi busy poll on client
      
      client_poll=100us+   41us                    39us
      server_poll=100us+
      prefer napi busy poll on server
      
      client_poll=100us+   41us                    39us
      server_poll=100us+
      prefer napi busy poll on client + server
      
      Signed-off-by: default avatarStefan Roesch <shr@devkernel.io>
      Suggested-by: default avatarOlivier Langlois <olivier@trillion01.com>
      Acked-by: default avatarJakub Kicinski <kuba@kernel.org>
      Link: https://lore.kernel.org/r/20230608163839.2891748-5-shr@devkernel.io
      
      
      Signed-off-by: default avatarJens Axboe <axboe@kernel.dk>
      8d0c12a8