Date: Wed, 25 Apr 2012 18:03:34 -0400 From: Andrew Boyer <aboyer@averesystems.com> To: Jack Vogel <jfvogel@gmail.com> Cc: freebsd-net@freebsd.org, Ryan Stone <rysto32@gmail.com>, Jack Vogel <jack.vogel@intel.com> Subject: Re: Bad interaction between 82599 hardware RSC and VLANs Message-ID: <131F4CD6-5C3B-4C43-85E8-726D87527290@averesystems.com> In-Reply-To: <CAFOYbc=ANdsMGXNGvjmkr=ecKVUQhFDDiK0%2Bvga_XB7m0JyB3Q@mail.gmail.com> References: <10A2858D-8DA8-45C4-B9A6-00CFA172404F@averesystems.com> <CAFOYbc=ANdsMGXNGvjmkr=ecKVUQhFDDiK0%2Bvga_XB7m0JyB3Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Any update on this?
-Andrew
On Jan 13, 2012, at 6:04 PM, Jack Vogel wrote:
> Hey Andrew,
>=20
> Not heard of this before, but I'll check around.
>=20
> Jack
>=20
>=20
> On Fri, Jan 13, 2012 at 3:01 PM, Andrew Boyer =
<aboyer@averesystems.com> wrote:
> Hello Jack,
> I'm seeing an issue on 82599 controllers. When hardware RSC is used, =
large VLAN packets arrive without the VP bit set, even though the vtag =
in the descriptor is correct. It totally kills the receive performance. =
Turning off hardware RSC in the driver (falling back to software LRO) =
works fine, as does turning off LRO entirely.
>=20
> I've worked around the problem for now by overriding the VP bit if =
ixgbe_rxeof() finds a valid vtag in the descriptor.
>=20
> Have you seen this before?
>=20
> It's not in the latest errata. It almost seems to be the opposite of =
what Ryan reported in November 2010 ("82599 receiving packets with vlan =
tag=3D0 (vlan strip problem)?").
>=20
> Thanks,
> Andrew
>=20
> --------------------------------------------------
> Andrew Boyer aboyer@averesystems.com
>=20
>=20
>=20
>=20
> _______________________________________________
> 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"
>=20
--------------------------------------------------
Andrew Boyer aboyer@averesystems.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?131F4CD6-5C3B-4C43-85E8-726D87527290>