Date: Sat, 18 May 2013 12:54:27 -0700 (PDT) From: Laurie Jennings <laurie_jennings_1977@yahoo.com> To: Jack Vogel <jfvogel@gmail.com> Cc: FreeBSD Net <freebsd-net@freebsd.org> Subject: Re: Is there any way to limit the amount of data in an mbuf chain submitted to a driver? Message-ID: <1368906867.48056.YahooMailClassic@web125806.mail.ne1.yahoo.com> In-Reply-To: <CAFOYbckvv1-cNv_upiBWQQOdomq4g_X%2BjcBv-0SUU6JSG%2BPajQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I have to make a case to wait for the new version or to deploy the current = version. Are there structural improvements to the driver, or just peripheral feature= s? We're usingx540 NICs. Laurie --- On Sat, 5/18/13, Jack Vogel <jfvogel@gmail.com> wrote: From: Jack Vogel <jfvogel@gmail.com> Subject: Re: Is there any way to limit the amount of data in an mbuf chain = submitted to a driver? To: "Laurie Jennings" <laurie_jennings_1977@yahoo.com> Cc: "FreeBSD Net" <freebsd-net@freebsd.org> Date: Saturday, May 18, 2013, 9:16 AM Version numbers result from my work internally, and sometimes they increment due to a build issue, or a bug found that needs to be corrected, so unfortunately its not always a neat progression. I have thought at times about having a separate revision sequence but that would make for other issues, also not ever change made into the community source changes the version either. Its all because of the driver living in two different worlds you might say :) I don't have the list at hand right now, what were you planning to deploy instead? Jack On Sat, May 18, 2013 at 5:08 AM, Laurie Jennings < laurie_jennings_1977@yahoo.com> wrote: > Can you outline the changes? Anything with the general processing? I have > to make > a case to hold off a deployment. > > and what happened to 9, 10, and 11? > > Laurie > > > --- On *Fri, 5/17/13, Jack Vogel <jfvogel@gmail.com>* wrote: > > > From: Jack Vogel <jfvogel@gmail.com> > Subject: Re: Is there any way to limit the amount of data in an mbuf chai= n > submitted to a driver? > To: "Laurie Jennings" <laurie_jennings_1977@yahoo.com> > Cc: "FreeBSD Net" <freebsd-net@freebsd.org>, "Adrian Chadd" < > adrian@freebsd.org>, "Richard Sharpe" <realrichardsharpe@gmail.com> > Date: Friday, May 17, 2013, 3:32 PM > > No Laurie, I ran into an issue that I needed to resolve, and then my > validation engineer > went out of town a couple days. Should be early next week. > > Jack > > > > On Fri, May 17, 2013 at 3:25 PM, Laurie Jennings < > laurie_jennings_1977@yahoo.com<http://mc/compose?to=3Dlaurie_jennings_197= 7@yahoo.com>> > wrote: > > > Did you get to commit that new code yet? > > > > Laurie > > > > --- On *Sat, 5/4/13, Jack Vogel <jfvogel@gmail.com<http://mc/compose?to= =3Djfvogel@gmail.com>>* > wrote: > > > > > > From: Jack Vogel <jfvogel@gmail.com<http://mc/compose?to=3Djfvogel@gmai= l.com> > > > > Subject: Re: Is there any way to limit the amount of data in an mbuf > chain > > submitted to a driver? > > To: "Richard Sharpe" <realrichardsharpe@gmail.com<http://mc/compose?to= =3Drealrichardsharpe@gmail.com> > > > > Cc: "FreeBSD Net" <freebsd-net@freebsd.org<http://mc/compose?to=3Dfreeb= sd-net@freebsd.org>>, > "Adrian Chadd" < > > adrian@freebsd.org <http://mc/compose?to=3Dadrian@freebsd.org>>; > > Date: Saturday, May 4, 2013, 2:18 PM > > > > > > Ahh, Twinville, new hardware :)=C2=A0 The version at the tip is 2.5.8 a= nd I am > > working on version 2.5.12 internally that I hope to commit next week... > > so your version is "a bit old" :) I would do some testing on newer code= . > > > > Jack > > > > > > > > On Sat, May 4, 2013 at 1:54 PM, Richard Sharpe > > <realrichardsharpe@gmail.com<http://mc/compose?to=3Drealrichardsharpe@g= mail.com> > <http://mc/compose?to=3Drealrichardsharpe@gmail.com>; > > >wrote: > > > > > On Sat, May 4, 2013 at 1:41 PM, Jack Vogel <jfvogel@gmail.com<http://= mc/compose?to=3Djfvogel@gmail.com> > <http://mc/compose?to=3Djfvogel@gmail.com>>; > > > wrote: > > > > If you don't use TSO you will hurt your TX performance significantl= y > > from > > > > the tests that I've run. What exactly is the device you are using, = I > > > don't > > > > have the source in front of me now, but I'm almost sure that the > limit > > is > > > > not 64K but 256K, or are you using some ancient version of the > driver? > > > > > >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0=C2=A0ix0 pnpinfo vendo= r=3D0x8086 device=3D0x1528 subvendor=3D0x8086 > > > subdevice=3D0x0001 class=3D0x020000 at slot=3D0 function=3D0 > > >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0=C2=A0ix1 pnpinfo vendo= r=3D0x8086 device=3D0x1528 subvendor=3D0x8086 > > > subdevice=3D0x0001 class=3D0x020000 at slot=3D0 function=3D1 > > > > > > The version calls itself ixgbe-2.4.4 ... > > > > > > Hmmm, copyright is 2001-2010 ... so perhaps a bit old. > > > > > > > Jack > > > > > > > > > > > > > > > > On Sat, May 4, 2013 at 1:30 PM, Richard Sharpe < > > > realrichardsharpe@gmail.com<http://mc/compose?to=3Drealrichardsharpe@= gmail.com> > <http://mc/compose?to=3Drealrichardsharpe@gmail.com>; > > > > > > > wrote: > > > >> > > > >> On Sat, May 4, 2013 at 10:39 AM, Adrian Chadd <adrian@freebsd.org<= http://mc/compose?to=3Dadrian@freebsd.org>; > <http://mc/compose?to=3Dadrian@freebsd.org>; > > > > > > wrote: > > > >> > On 4 May 2013 06:52, Richard Sharpe <realrichardsharpe@gmail.com= <http://mc/compose?to=3Drealrichardsharpe@gmail.com>; > <http://mc/compose?to=3Drealrichardsharpe@gmail.com>; > > > > > > > wrote: > > > >> >> Hi folks, > > > >> >> > > > >> >> I understand better why I am seeing EINVAL intermittently when > > > sending > > > >> >> data from Samba via SMB2. > > > >> >> > > > >> >> The ixgbe driver, for TSO reasons, limits the amount of data th= at > > can > > > >> >> be DMA'd to 65535 bytes. It returns EINVAL for any mbuf chain > > larger > > > >> >> than that. > > > >> >> > > > >> >> The SO_SNDBUF for that socket is set to 131972. Mostly there is > > less > > > >> >> than 64kiB of space available, so that is all TCP etc can put > into > > > the > > > >> >> socket in one chain of mbufs. However, every now and then there > is > > > >> >> more than 65535 bytes available in the socket buffers, and we > have > > an > > > >> >> SMB packet that is larger than 65535 bytes, and we get hit. > > > >> >> > > > >> >> To confirm this I am going to set SO_SNDBUF back to the default > of > > > >> >> 65536 and test again. My repros are very reliable. > > > >> >> > > > >> >> However, I wondered if my only way around this if I want to > > continue > > > >> >> to use SO_SNDBUF sizes larger than 65536 is to fragment large > mbuf > > > >> >> chains in the driver? > > > >> > > > > >> > Hm, is this is a problem without TSO? > > > >> > > > >> We are using the card without TSO, so I am thinking of changing th= at > > > >> limit to 131072 and retesting. > > > >> > > > >> I am currently testing with SO_SNDBUF=3D32768 and have not hit the > > > problem. > > > >> > > > >> > Is the problem that the NIC can't handle a frame that big, or a > > buffer > > > >> > that big? > > > >> > Ie - if you handed the hardware two descriptors of 64k each, for > the > > > >> > same IP datagram, will it complain? > > > >> > > > >> I can't find any documentation, but it seems that with TSO it cann= ot > > > >> handle a frame that big. Actually, since we are not using TSO, the= re > > > >> really should not be a problem with larger frames. > > > >> > > > >> > Or do you need to break it up into two separate IP datagrams, > facing > > > >> > the driver, with a maximum size of 64k each? > > > >> > > > >> Not sure, but it looks like we need to do that. > > > >> > > > >> > > > >> -- > > > >> Regards, > > > >> Richard Sharpe > > > >> (=E4=BD=95=E4=BB=A5=E8=A7=A3=E6=86=82=EF=BC=9F=E5=94=AF=E6=9C=89= =E6=9D=9C=E5=BA=B7=E3=80=82--=E6=9B=B9=E6=93=8D) > > > >> _______________________________________________ > > > >> freebsd-net@freebsd.org<http://mc/compose?to=3Dfreebsd-net@freebsd= .org> > <http://mc/compose?to=3Dfreebsd-net@freebsd.org>mailing list > > > >> http://lists.freebsd.org/mailman/listinfo/freebsd-net > > > >> To unsubscribe, send any mail to " > freebsd-net-unsubscribe@freebsd.org<http://mc/compose?to=3Dfreebsd-net-un= subscribe@freebsd.org> > <http://mc/compose?to=3Dfreebsd-net-unsubscribe@freebsd.org>; > > > " > > > > > > > > > > > > > > > > > > > > -- > > > Regards, > > > Richard Sharpe > > > (=E4=BD=95=E4=BB=A5=E8=A7=A3=E6=86=82=EF=BC=9F=E5=94=AF=E6=9C=89=E6= =9D=9C=E5=BA=B7=E3=80=82--=E6=9B=B9=E6=93=8D) > > > > > _______________________________________________ > > freebsd-net@freebsd.org <http://mc/compose?to=3Dfreebsd-net@freebsd.org= > < > http://mc/compose?to=3Dfreebsd-net@freebsd.org>mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-net > > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org<h= ttp://mc/compose?to=3Dfreebsd-net-unsubscribe@freebsd.org> > <http://mc/compose?to=3Dfreebsd-net-unsubscribe@freebsd.org>; > > > " > > > > > _______________________________________________ > freebsd-net@freebsd.org <http://mc/compose?to=3Dfreebsd-net@freebsd.org>m= ailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org<htt= p://mc/compose?to=3Dfreebsd-net-unsubscribe@freebsd.org> > " > > _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Sat May 18 20:00:01 2013 Return-Path: <owner-freebsd-net@FreeBSD.ORG> Delivered-To: freebsd-net@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E2E42AD0 for <freebsd-net@smarthost.ysv.freebsd.org>; Sat, 18 May 2013 20:00:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id BB4C1D4 for <freebsd-net@smarthost.ysv.freebsd.org>; Sat, 18 May 2013 20:00:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r4IK01k5088709 for <freebsd-net@freefall.freebsd.org>; Sat, 18 May 2013 20:00:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r4IK01A1088708; Sat, 18 May 2013 20:00:01 GMT (envelope-from gnats) Date: Sat, 18 May 2013 20:00:01 GMT Message-Id: <201305182000.r4IK01A1088708@freefall.freebsd.org> To: freebsd-net@FreeBSD.org Cc: From: Mykhaylo Yehorov <yehorov@gmail.com> Subject: Re: kern/167059: [tcp] [panic] System does panic in in_pcbbind() and hangs X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Mykhaylo Yehorov <yehorov@gmail.com> List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-net>, <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>; List-Post: <mailto:freebsd-net@freebsd.org> List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>, <mailto:freebsd-net-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 18 May 2013 20:00:01 -0000 The following reply was made to PR kern/167059; it has been noted by GNATS. From: Mykhaylo Yehorov <yehorov@gmail.com> To: Mikolaj Golub <trociny@freebsd.org> Cc: bug-followup@freebsd.org Subject: Re: kern/167059: [tcp] [panic] System does panic in in_pcbbind() and hangs Date: Sat, 18 May 2013 22:51:00 +0300 --089e0158b44c3cc80904dd036b4d Content-Type: text/plain; charset=UTF-8 We use our software on FreeBSD 9.X without any kernel panics for a year. On Sat, May 18, 2013 at 10:15 PM, Mikolaj Golub <trociny@freebsd.org> wrote: > This looks similar to the issue fixed in 9.0 (r227207 + r227449). > > There was a discussion on freebsd-net@ titled "Kernel panic on FreeBSD > 9.0-beta2": > > > http://lists.freebsd.org/pipermail/freebsd-net/2011-September/029858.html > > Are there chances that you can check >=9.0? > > -- > Mikolaj Golub > -- Mykhaylo Yehorov --089e0158b44c3cc80904dd036b4d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">We use our software on FreeBSD 9.X without any kernel pani= cs for a year.<br></div><div class=3D"gmail_extra"><br><br><div class=3D"gm= ail_quote">On Sat, May 18, 2013 at 10:15 PM, Mikolaj Golub <span dir=3D"ltr= "><<a href=3D"mailto:trociny@freebsd.org" target=3D"_blank">trociny@free= bsd.org</a>></span> wrote:<br> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex">This looks similar to the issue fixed in 9.0= (r227207 + r227449).<br> <br> There was a discussion on freebsd-net@ titled "Kernel panic on FreeBSD= <br> 9.0-beta2":<br> <br> =C2=A0 <a href=3D"http://lists.freebsd.org/pipermail/freebsd-net/2011-Septe= mber/029858.html" target=3D"_blank">http://lists.freebsd.org/pipermail/free= bsd-net/2011-September/029858.html</a><br> <br> Are there chances that you can check >=3D9.0?<br> <span class=3D"HOEnZb"><font color=3D"#888888"><br> --<br> Mikolaj Golub<br> </font></span></blockquote></div><br><br clear=3D"all"><br>-- <br>Mykhaylo = Yehorov </div> --089e0158b44c3cc80904dd036b4d--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1368906867.48056.YahooMailClassic>