Re: [PREEMPT-RT] [patch 4 14/22] timer: Switch to a non cascading wheel

On Wed, Aug 17, 2016 at 12:05:22PM +0300, Jouni Malinen wrote: > I had not realized this previously due to the test case passing, but the > same retransmit SYN case was happening with older kernels, it just was > done a tiny bit faster to escape that 1.0 second timeout limit.. That > about 1.03

Re: [PREEMPT-RT] [patch 4 14/22] timer: Switch to a non cascading wheel

On Wed, Aug 17, 2016 at 12:05:22PM +0300, Jouni Malinen wrote: > I had not realized this previously due to the test case passing, but the > same retransmit SYN case was happening with older kernels, it just was > done a tiny bit faster to escape that 1.0 second timeout limit.. That > about 1.03

Re: [PREEMPT-RT] [patch 4 14/22] timer: Switch to a non cascading wheel

On Tue, Aug 16, 2016 at 11:46:00AM +0200, Richard Cochran wrote: > If I understand the test correctly, then the slightly different kernel > timer behavior is ok, but the test isn't quite right. Let explain > what I mean. > > First off, reading test_ap_wps.py, the point of the test is to see if >

Re: [PREEMPT-RT] [patch 4 14/22] timer: Switch to a non cascading wheel

On Tue, Aug 16, 2016 at 11:46:00AM +0200, Richard Cochran wrote: > If I understand the test correctly, then the slightly different kernel > timer behavior is ok, but the test isn't quite right. Let explain > what I mean. > > First off, reading test_ap_wps.py, the point of the test is to see if >

Re: [PREEMPT-RT] [patch 4 14/22] timer: Switch to a non cascading wheel

On Tue, Aug 16, 2016 at 5:46 AM, Richard Cochran wrote: > Jouni, > > If I understand the test correctly, then the slightly different kernel > timer behavior is ok, but the test isn't quite right. Let explain > what I mean. > > First off, reading test_ap_wps.py, the

Re: [PREEMPT-RT] [patch 4 14/22] timer: Switch to a non cascading wheel

On Tue, Aug 16, 2016 at 5:46 AM, Richard Cochran wrote: > Jouni, > > If I understand the test correctly, then the slightly different kernel > timer behavior is ok, but the test isn't quite right. Let explain > what I mean. > > First off, reading test_ap_wps.py, the point of the test is to see if

Re: [PREEMPT-RT] [patch 4 14/22] timer: Switch to a non cascading wheel

Jouni, If I understand the test correctly, then the slightly different kernel timer behavior is ok, but the test isn't quite right. Let explain what I mean. First off, reading test_ap_wps.py, the point of the test is to see if ten simultaneous connections are possible. I guess the server

Re: [PREEMPT-RT] [patch 4 14/22] timer: Switch to a non cascading wheel

Jouni, If I understand the test correctly, then the slightly different kernel timer behavior is ok, but the test isn't quite right. Let explain what I mean. First off, reading test_ap_wps.py, the point of the test is to see if ten simultaneous connections are possible. I guess the server

Re: [PREEMPT-RT] [patch 4 14/22] timer: Switch to a non cascading wheel

On Thu, Aug 11, 2016 at 11:25 PM, wrote: > On Thu, Aug 11, 2016 at 06:21:26PM +0300, Jouni Malinen wrote: >> The test code looked like this in python: >> >> addr = (url.hostname, url.port) >> socks = {} >> for i in range(20): >> socks[i] =

Re: [PREEMPT-RT] [patch 4 14/22] timer: Switch to a non cascading wheel

On Thu, Aug 11, 2016 at 11:25 PM, wrote: > On Thu, Aug 11, 2016 at 06:21:26PM +0300, Jouni Malinen wrote: >> The test code looked like this in python: >> >> addr = (url.hostname, url.port) >> socks = {} >> for i in range(20): >> socks[i] = socket.socket(socket.AF_INET,

Re: [PREEMPT-RT] [patch 4 14/22] timer: Switch to a non cascading wheel

On Thu, Aug 11, 2016 at 06:21:26PM +0300, Jouni Malinen wrote: > The test code looked like this in python: > > addr = (url.hostname, url.port) > socks = {} > for i in range(20): > socks[i] = socket.socket(socket.AF_INET, socket.SOCK_STREAM, >

Re: [PREEMPT-RT] [patch 4 14/22] timer: Switch to a non cascading wheel

On Thu, Aug 11, 2016 at 06:21:26PM +0300, Jouni Malinen wrote: > The test code looked like this in python: > > addr = (url.hostname, url.port) > socks = {} > for i in range(20): > socks[i] = socket.socket(socket.AF_INET, socket.SOCK_STREAM, >