On 2/15/2019 11:18 AM, Cong Wang wrote:
On Thu, Feb 14, 2019 at 4:43 PM Samudrala, Sridhar
wrote:
On 2/14/2019 12:15 PM, Cong Wang wrote:
Hello,
While looking into the busy polling in Linux kernel, three questions
come into my mind:
1. In the document[1], it claims sysctl.net.busy_poll de
On Mon, Feb 18, 2019 at 11:30 PM Cong Wang wrote:
>
> On Fri, Feb 15, 2019 at 2:47 PM Willem de Bruijn
> wrote:
> >
> > > > > 2. Why there is no socket option for sysctl.net.busy_poll? Clearly
> > > > > sysctl_net_busy_poll is global and SO_BUSY_POLL only works for
> > > > > sysctl.net.busy_read.
On Fri, Feb 15, 2019 at 2:47 PM Willem de Bruijn
wrote:
>
> > > > 2. Why there is no socket option for sysctl.net.busy_poll? Clearly
> > > > sysctl_net_busy_poll is global and SO_BUSY_POLL only works for
> > > > sysctl.net.busy_read.
> > >
> > > I guess because of how sock_poll works. In that case
> > > 2. Why there is no socket option for sysctl.net.busy_poll? Clearly
> > > sysctl_net_busy_poll is global and SO_BUSY_POLL only works for
> > > sysctl.net.busy_read.
> >
> > I guess because of how sock_poll works. In that case it is not needed.
> > The poll duration applies more to the pollset
On Thu, Feb 14, 2019 at 4:39 PM Willem de Bruijn
wrote:
>
> On Thu, Feb 14, 2019 at 3:15 PM Cong Wang wrote:
> >
> > Hello,
> >
> > While looking into the busy polling in Linux kernel, three questions
> > come into my mind:
> >
> > 1. In the document[1], it claims sysctl.net.busy_poll depends on
On Thu, Feb 14, 2019 at 4:43 PM Samudrala, Sridhar
wrote:
>
>
> On 2/14/2019 12:15 PM, Cong Wang wrote:
>
> Hello,
>
> While looking into the busy polling in Linux kernel, three questions
> come into my mind:
>
> 1. In the document[1], it claims sysctl.net.busy_poll depends on
> either SO_BUSY_POL
On Thu, Feb 14, 2019 at 3:15 PM Cong Wang wrote:
>
> Hello,
>
> While looking into the busy polling in Linux kernel, three questions
> come into my mind:
>
> 1. In the document[1], it claims sysctl.net.busy_poll depends on
> either SO_BUSY_POLL or sysctl.net.busy_read. However, from the code in
>