[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1349762863.21172.3848.camel@edumazet-glaptop>
Date: Tue, 09 Oct 2012 08:07:43 +0200
From: Eric Dumazet <eric.dumazet@...il.com>
To: Frank Reppin <frank@...ermydesk.org>
Cc: netdev@...r.kernel.org, Jeff Kirsher <jeffrey.t.kirsher@...el.com>
Subject: Re: [PATCH net] e1000e: Change wthresh to 1 to avoid possible Tx
stalls.
On Tue, 2012-10-09 at 00:25 +0000, Frank Reppin wrote:
> Jeff Kirsher <jeffrey.t.kirsher <at> intel.com> writes:
> >
> > On Thu, 2012-06-07 at 06:24 +0200, Eric Dumazet wrote:
> > > On Wed, 2012-06-06 at 17:59 -0700, Jeff Kirsher wrote:
> > >
> > > > After further internal review, NACK.
> > > >
> > > > This patch will cause unacceptable performance issues with non-ESB2
> > > > parts.
> > > >
> > > > I am dropping this patch from my queue.
> > > >
> > >
> > > I'd like you share your performance numbers before NACKing this patch.
> > >
> > > What is the alternative patch you guys have ?
> > >
> >
> > Jesse did not share any performance numbers with me, I am sure he can
> > give some background tomorrow when he is back online.
> >
> > I am working on an alternative patch now and should have something to
> > share tomorrow.
> Please allow me to ask if there's any progess here?
>
> I've tried 3.5.4 a couple of days ago on a SuperMicro X8SIE-LN4 (82574L)
> and could still observe severe latency (up to 3000ms) spikes.
>
> Applying Hiroakis suggested patch did fix this for me as well.
> [please note as well that I didn't had this issue in any 3.4.x kernel
> before - so +1 for fixing the regression]
Its a shame this bug is not yet fixed.
I dont know what to say.
--
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