[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1415202075.12206.0.camel@edumazet-glaptop2.roam.corp.google.com>
Date: Wed, 05 Nov 2014 07:41:15 -0800
From: Eric Dumazet <eric.dumazet@...il.com>
To: Ezequiel Garcia <ezequiel.garcia@...e-electrons.com>
Cc: Karl Beldan <karl.beldan@...il.com>,
David Miller <davem@...emloft.net>,
Ian Campbell <ijc@...lion.org.uk>,
Karl Beldan <karl.beldan@...ierawaves.com>,
netdev@...r.kernel.org,
Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>
Subject: Re: [PATCH] net: mv643xx_eth: reclaim TX skbs only when released by
the HW
On Wed, 2014-11-05 at 11:46 -0300, Ezequiel Garcia wrote:
> Hi Karl,
>
> On 11/05/2014 11:32 AM, Karl Beldan wrote:> From: Karl Beldan <karl.beldan@...ierawaves.com>
> >
> > ATM, txq_reclaim will dequeue and free an skb for each tx desc released
> > by the hw that has TX_LAST_DESC set. However, in case of TSO, each
> > hw desc embedding the last part of a segment has TX_LAST_DESC set,
> > losing the one-to-one 'last skb frag'/'TX_LAST_DESC set' correspondance,
> > which causes data corruption.
> >
> > Fix this by checking TX_ENABLE_INTERRUPT instead of TX_LAST_DESC, and
> > warn when trying to dequeue from an empty txq (which can be symptomatic
> > of releasing skbs prematurely).
> >
> > Fixes: 3ae8f4e0b98 ('net: mv643xx_eth: Implement software TSO')
>
> Although your change makes sense, this isn't fixing the issue for me,
> neither did the previous one.
>
> Ian: Can you double check that you have corruption *without* the patch,
> and that the patch fixes the issue?
>
Have you also applied my patch ?
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists