Re: setsockopt() weirdness

2002-07-14 Thread Luigi Rizzo
On Sun, Jul 14, 2002 at 12:43:51PM -0400, David Miller wrote: > On Sun, 14 Jul 2002, Luigi Rizzo wrote: > > > On Sun, Jul 14, 2002 at 11:49:46AM -0400, David Miller wrote: > > ... > > > HZ is set to 5000; the machine is intended to process several tens of > > > thousands of very small packets per

Re: setsockopt() weirdness

2002-07-14 Thread David Miller
On Sun, 14 Jul 2002, Luigi Rizzo wrote: > On Sun, Jul 14, 2002 at 11:49:46AM -0400, David Miller wrote: > ... > > HZ is set to 5000; the machine is intended to process several tens of > > thousands of very small packets per second, and interrupt processing was a > > big problem. > > why don't yo

Re: setsockopt() weirdness

2002-07-14 Thread Luigi Rizzo
On Sun, Jul 14, 2002 at 11:49:46AM -0400, David Miller wrote: ... > HZ is set to 5000; the machine is intended to process several tens of > thousands of very small packets per second, and interrupt processing was a > big problem. why don't you use "options DEVICE_POLLING" then :) > Does this mea

Re: setsockopt() weirdness

2002-07-14 Thread David Miller
On Sun, 14 Jul 2002, Luigi Rizzo wrote: > On Sun, Jul 14, 2002 at 10:49:56AM -0400, David Miller wrote: > > I'm probably doing something basic wrong, but I'm getting a very > > inconsistent response when using setsockopt to set the SO_RCVTIMEO to > > seven seconds or more. > > i would suspect so

Re: setsockopt() weirdness

2002-07-14 Thread Luigi Rizzo
On Sun, Jul 14, 2002 at 10:49:56AM -0400, David Miller wrote: > I'm probably doing something basic wrong, but I'm getting a very > inconsistent response when using setsockopt to set the SO_RCVTIMEO to > seven seconds or more. i would suspect some overflow of 16-bit fields used to store the timeou