[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1490412855.24891.10.camel@edumazet-glaptop3.roam.corp.google.com>
Date: Fri, 24 Mar 2017 20:34:15 -0700
From: Eric Dumazet <eric.dumazet@...il.com>
To: Alexander Duyck <alexander.duyck@...il.com>
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
sridhar.samudrala@...el.com, edumazet@...gle.com,
davem@...emloft.net, linux-api@...r.kernel.org
Subject: Re: [net-next PATCH v3 5/8] net: Track start of busy loop instead
of when it should end
On Fri, 2017-03-24 at 10:08 -0700, Alexander Duyck wrote:
> From: Alexander Duyck <alexander.h.duyck@...el.com>
>
> This patch flips the logic we were using to determine if the busy polling
> has timed out. The main motivation for this is that we will need to
> support two different possible timeout values in the future and by
> recording the start time rather than when we would want to end we can focus
> on making the end_time specific to the task be it epoll or socket based
> polling.
>
> Signed-off-by: Alexander Duyck <alexander.h.duyck@...el.com>
> ---
Acked-by: Eric Dumazet <edumazet@...gle.com>
Thanks guys !
Powered by blists - more mailing lists