Date: Tue, 11 Feb 2014 15:35:15 -0800 From: Adrian Chadd <adrian@freebsd.org> To: Egoitz Aurrekoetxea <egoitz@ramattack.net> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: mbuf_tag memory freeing issues with LRO enabled on the XENHVM driver Message-ID: <CAJ-VmonkTLMbEA7sY76U4pKZUMHzTrcvKMt0rct_q-7ViUJY9w@mail.gmail.com> In-Reply-To: <1AECA876-08BC-48F8-B356-42CE35100805@ramattack.net> References: <1AECA876-08BC-48F8-B356-42CE35100805@ramattack.net>
next in thread | previous in thread | raw e-mail | index | archive | help
+net
.. any ideas?
-a
On 11 February 2014 10:05, Egoitz Aurrekoetxea <egoitz@ramattack.net> wrote:
> Good afternoon,
>
> It seems the LRO code inside the FreeBSD's kernel is causing the first mbuf chain's anymbuf->m_hdr->mh_flags due to some failure not to contain the M_PKTHDR flag.
> Have you ever seen this bad behavior with any of these drivers having LRO enabled :
>
> cxgb
> cxgbe
> e1000
> ixgbe
> ixgbe
> mxge
> oce
> qlxgb
> qlxge
> virtio
> vxge
>
> The no presence of this flag, seems to be causing the kernel not to be able to enter :
>
> static void
> mb_dtor_pack(void *mem, int size, void *arg)
> {
> struct mbuf *m;
>
> m = (struct mbuf *)mem;
> if ((m->m_flags & M_PKTHDR) != 0)
> m_tag_delete_chain(m, NULL); <============ to this function.
>
> causing the wired memory to increase a lot due mbuf_tags usage memory to be pretty high.
>
> I have noticed about this issue using the XENHVM network driver (xn), but taking a look at some other drivers using the same code as this one... have found the commented before ones....
>
> Has anyone too suffered the issue?.
>
> Best regards,
>
>
> _______________________________________________
> freebsd-hackers@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmonkTLMbEA7sY76U4pKZUMHzTrcvKMt0rct_q-7ViUJY9w>