[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.0.9999.0711150846280.2786@woody.linux-foundation.org>
Date: Thu, 15 Nov 2007 08:48:58 -0800 (PST)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Greg KH <gregkh@...e.de>
cc: linux-kernel@...r.kernel.org, stable@...nel.org,
Justin Forbes <jmforbes@...uxtx.org>,
Zwane Mwaikambo <zwane@....linux.org.uk>,
"Theodore Ts'o" <tytso@....edu>,
Randy Dunlap <rdunlap@...otime.net>,
Dave Jones <davej@...hat.com>,
Chuck Wolber <chuckw@...ntumlinux.com>,
Chris Wedgwood <reviews@...cw.f00f.org>,
Michael Krufky <mkrufky@...uxtv.org>,
Chuck Ebbert <cebbert@...hat.com>,
Domenico Andreoli <cavokz@...il.com>,
akpm@...ux-foundation.org, alan@...rguk.ukuu.org.uk,
Stephen Hemminger <shemminger@...ux-foundation.org>,
Jeff Garzik <jeff@...zik.org>
Subject: Re: [patch 08/16] skge: fix ram buffer size calculation
On Thu, 15 Nov 2007, Greg KH wrote:
> On Thu, Nov 15, 2007 at 08:11:30AM -0800, Linus Torvalds wrote:
> > >
> > > patch 7fb7ac241162dc51ec0f7644d4a97b2855213c32 in mainline.
> >
> > This one is getting reverted in mainline in about five minutes (unless I
> > find an email from Stephen to address the reported regression - I haven't
> > gone through all my emails yet), so I don't think it should make it into
> > stable.
>
> Thanks for letting me know which patch is causing the problem, I just
> got another report of the skge driver not working with all of these
> patches applied.
I suspect that's the same report.
> It looks like I'll just drop this one from the patch list, unless
> Stephen has a better idea.
This is my commit message for the revert - note the suggested possible
fix (but also why I didn't apply it, and why things got reverted).
Linus
---
commit 279e1dab949d33737557babfe9f74e0b74fbe39a
Author: Linus Torvalds <torvalds@...dy.linux-foundation.org>
Date: Thu Nov 15 08:44:36 2007 -0800
Revert "skge: fix ram buffer size calculation"
This reverts commit 7fb7ac241162dc51ec0f7644d4a97b2855213c32.
Heikki Orsila reports that it causes a regression:
"Doing
nc host port < /dev/zero
on a sending machine (not skge) to an skge machine that is receiving:
nc -l -p port >/dev/null
with ~60 MiB/s speed, causes the interface go malfunct. A slow
transfer doesn't cause a problem."
See
http://bugzilla.kernel.org/show_bug.cgi?id=9321
for some more information.
There is a workaround (also reported by Heikki):
"After some fiddling, I noticed that not changing the register write
order on patch:
+ skge_write32(hw, RB_ADDR(q, RB_END), end);
skge_write32(hw, RB_ADDR(q, RB_WP), start);
skge_write32(hw, RB_ADDR(q, RB_RP), start);
- skge_write32(hw, RB_ADDR(q, RB_END), end);
fixes the visible effect.. Possibly not the root cause of the
problem, but changing the order back fixes networking here."
but that has yet to be ack'ed or tested more widely, so the whole
problem-causing commit gets reverted until this is resolved properly.
Bisected-and-requested-by: Heikki Orsila <shdl@...alwe.fi>
Cc: Stephen Hemminger <shemminger@...ux-foundation.org>
Cc: Jeff Garzik <jeff@...zik.org>
Signed-off-by: Linus Torvalds <torvalds@...ux-foundation.org>
drivers/net/skge.c | 51 +++++++++++++++++++++++++++------------------------
1 files changed, 27 insertions(+), 24 deletions(-)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists