lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 14 Feb 2019 12:15:31 -0800
From:   Cong Wang <>
To:     Alexander Duyck <>
Cc:     Eric Dumazet <>,,
        Linux Kernel Network Developers <>
Subject: Three questions about busy poll


While looking into the busy polling in Linux kernel, three questions
come into my mind:

1. In the document[1], it claims depends on
either SO_BUSY_POLL or However, from the code in
ep_set_busy_poll_napi_id(), I don't see such a dependency. It simply
checks sysctl_net_busy_poll and sk->sk_napi_id, but sk->sk_napi_id is
always set as long as we enable CONFIG_NET_RX_BUSY_POLL. So what I am
missing here?

2. Why there is no socket option for Clearly
sysctl_net_busy_poll is global and SO_BUSY_POLL only works for

3. How is SO_INCOMING_NAPI_ID supposed to be used? I can't find any
useful documents online. Any example or more detailed doc?



Powered by blists - more mailing lists