Re: Seeing EINVAL from writev on 8.0 to a non-blocking socket even though the data seems to hit the wire

2013-05-06 Thread Gleb Smirnoff
[I'm adding Jack Vogel, maintainer of ixgbe, to cc] On Fri, May 03, 2013 at 07:01:18PM -0700, Richard Sharpe wrote: R> On Fri, May 3, 2013 at 10:18 AM, Richard Sharpe R> wrote: R> > On Fri, May 3, 2013 at 7:39 AM, Eric van Gyzen wrote: R> >> On 05/02/2013 19:00, Richard Sharpe wrote: R> >>> On

Re: Seeing EINVAL from writev on 8.0 to a non-blocking socket even though the data seems to hit the wire

2013-05-05 Thread Julian Elischer
On 5/2/13 5:18 PM, Eitan Adler wrote: On 2 May 2013 20:14, Eitan Adler wrote: gprof in base valgrind --callgrind doxygen can also do this. I was reminded this was about the kernel, not userland, sorry for the noise. hey richard.. dtrace is your friend. (and I happen to know you have it on

Re: Seeing EINVAL from writev on 8.0 to a non-blocking socket even though the data seems to hit the wire

2013-05-03 Thread Richard Sharpe
On Fri, May 3, 2013 at 10:18 AM, Richard Sharpe wrote: > On Fri, May 3, 2013 at 7:39 AM, Eric van Gyzen wrote: >> On 05/02/2013 19:00, Richard Sharpe wrote: >>> On Thu, May 2, 2013 at 7:52 AM, Eric van Gyzen wrote: On 05/02/2013 08:48, Richard Sharpe wrote: > On Wed, May 1, 2013 at 9:34

Re: Seeing EINVAL from writev on 8.0 to a non-blocking socket even though the data seems to hit the wire

2013-05-03 Thread Richard Sharpe
On Fri, May 3, 2013 at 7:39 AM, Eric van Gyzen wrote: > On 05/02/2013 19:00, Richard Sharpe wrote: >> On Thu, May 2, 2013 at 7:52 AM, Eric van Gyzen wrote: >>> On 05/02/2013 08:48, Richard Sharpe wrote: On Wed, May 1, 2013 at 9:34 PM, Alfred Perlstein wrote: > On 5/1/13 8:03 PM, Richard

Re: Seeing EINVAL from writev on 8.0 to a non-blocking socket even though the data seems to hit the wire

2013-05-03 Thread Eric van Gyzen
On 05/02/2013 19:00, Richard Sharpe wrote: > On Thu, May 2, 2013 at 7:52 AM, Eric van Gyzen wrote: >> On 05/02/2013 08:48, Richard Sharpe wrote: >>> On Wed, May 1, 2013 at 9:34 PM, Alfred Perlstein wrote: On 5/1/13 8:03 PM, Richard Sharpe wrote: > Hi folks, > > I am checking to s

Re: Seeing EINVAL from writev on 8.0 to a non-blocking socket even though the data seems to hit the wire

2013-05-02 Thread Eitan Adler
On 2 May 2013 20:14, Eitan Adler wrote: > gprof in base > valgrind --callgrind > doxygen can also do this. > I was reminded this was about the kernel, not userland, sorry for the noise. -- Eitan Adler ___ freebsd-net@freebsd.org mailing list http://

Re: Seeing EINVAL from writev on 8.0 to a non-blocking socket even though the data seems to hit the wire

2013-05-02 Thread Eitan Adler
On 2 May 2013 20:00, Richard Sharpe wrote: > On Thu, May 2, 2013 at 7:52 AM, Eric van Gyzen wrote: >> On 05/02/2013 08:48, Richard Sharpe wrote: >>> On Wed, May 1, 2013 at 9:34 PM, Alfred Perlstein wrote: On 5/1/13 8:03 PM, Richard Sharpe wrote: > Hi folks, > > I am checking to

Re: Seeing EINVAL from writev on 8.0 to a non-blocking socket even though the data seems to hit the wire

2013-05-02 Thread Richard Sharpe
On Thu, May 2, 2013 at 7:52 AM, Eric van Gyzen wrote: > On 05/02/2013 08:48, Richard Sharpe wrote: >> On Wed, May 1, 2013 at 9:34 PM, Alfred Perlstein wrote: >>> On 5/1/13 8:03 PM, Richard Sharpe wrote: Hi folks, I am checking to see if there are any known bugs with respect to this

Re: Seeing EINVAL from writev on 8.0 to a non-blocking socket even though the data seems to hit the wire

2013-05-02 Thread Richard Sharpe
On Thu, May 2, 2013 at 7:52 AM, Eric van Gyzen wrote: > On 05/02/2013 08:48, Richard Sharpe wrote: >> On Wed, May 1, 2013 at 9:34 PM, Alfred Perlstein wrote: >>> On 5/1/13 8:03 PM, Richard Sharpe wrote: Hi folks, I am checking to see if there are any known bugs with respect to this

Re: Seeing EINVAL from writev on 8.0 to a non-blocking socket even though the data seems to hit the wire

2013-05-02 Thread Eric van Gyzen
On 05/02/2013 08:48, Richard Sharpe wrote: > On Wed, May 1, 2013 at 9:34 PM, Alfred Perlstein wrote: >> On 5/1/13 8:03 PM, Richard Sharpe wrote: >>> Hi folks, >>> >>> I am checking to see if there are any known bugs with respect to this >>> in FreeBSD 8.0. >>> >>> Situation is that Samba 3.6.6 use

Re: Seeing EINVAL from writev on 8.0 to a non-blocking socket even though the data seems to hit the wire

2013-05-02 Thread Richard Sharpe
On Wed, May 1, 2013 at 9:34 PM, Alfred Perlstein wrote: > On 5/1/13 8:03 PM, Richard Sharpe wrote: >> Hi folks, >> >> I am checking to see if there are any known bugs with respect to this >> in FreeBSD 8.0. >> >> Situation is that Samba 3.6.6 uses writev to a non-blocking socket to >> get the SMB2

Re: Seeing EINVAL from writev on 8.0 to a non-blocking socket even though the data seems to hit the wire

2013-05-01 Thread Richard Sharpe
On Wed, May 1, 2013 at 9:34 PM, Alfred Perlstein wrote: > On 5/1/13 8:03 PM, Richard Sharpe wrote: >> Hi folks, >> >> I am checking to see if there are any known bugs with respect to this >> in FreeBSD 8.0. >> >> Situation is that Samba 3.6.6 uses writev to a non-blocking socket to >> get the SMB2

Re: Seeing EINVAL from writev on 8.0 to a non-blocking socket even though the data seems to hit the wire

2013-05-01 Thread Alfred Perlstein
On 5/1/13 8:03 PM, Richard Sharpe wrote: > Hi folks, > > I am checking to see if there are any known bugs with respect to this > in FreeBSD 8.0. > > Situation is that Samba 3.6.6 uses writev to a non-blocking socket to > get the SMB2 requests on the wire. > > Intermittently, we see the writev retur

Seeing EINVAL from writev on 8.0 to a non-blocking socket even though the data seems to hit the wire

2013-05-01 Thread Richard Sharpe
Hi folks, I am checking to see if there are any known bugs with respect to this in FreeBSD 8.0. Situation is that Samba 3.6.6 uses writev to a non-blocking socket to get the SMB2 requests on the wire. Intermittently, we see the writev return EINVAL even though the data has gotten on the wire. Th