[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100727224631.GO17248@us.ibm.com>
Date: Tue, 27 Jul 2010 17:46:31 -0500
From: Sonny Rao <sonnyrao@...ibm.com>
To: Jeff Kirsher <jeffrey.t.kirsher@...el.com>
Cc: netdev@...r.kernel.org, e1000-devel@...ts.sf.net
Subject: Re: [PATCH] Add missing memory barriers to clean_rx_irq functions
in Intel Drivers
On Tue, Jul 27, 2010 at 03:41:46PM -0700, Jeff Kirsher wrote:
> On Tue, Jul 27, 2010 at 15:34, Sonny Rao <sonnyrao@...ibm.com> wrote:
> > This patch is similar to what was fixed in ixgbe in this patch:
> >
> > http://marc.info/?l=e1000-devel&m=126593062701537&w=3
> >
> > We should add read memory barriers to all the similar cases across the
> > Intel ethernet driver family. In the case of ixgbevf I've also added
> > a missing barrier to the clean_tx_irq path because I missed it in my
> > last patch.
> >
> > Without the barrier a processor can speculate a load ahead of the load
> > which looks at the status bit and get stale information causing a
> > number of different issues including invalid packet length, NULL
> > pointers, or bad data since checksumming was assumed to be done
> > in hardware.
> >
> > Signed-off-by: Milton Miller <miltonm@....com>
> > Signed-off-by: Sonny Rao <sonnyrao@...ibm.com>
> > cc: stable <stable@...nel.org>
> >
>
> I already have a similar patch in my queue from you Sonny, although I
> see that this patch has made a few more changes. Is this version 2?
Well, the previous one was for the clean_tx_irq functions this one is
for the clean_rx_irq functions. I'd gotten the two confused when I
referenced Anton's original patch -- which was also a clean_rx_irq
patch. So they are touching different code paths but fixing similar
problems.
--
Sonny Rao, LTC OzLabs, BML team
--
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