From: Willy Tarreau <w@1wt.eu>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: Linux 2.6.32.61
Date: Fri, 14 Jun 2013 07:54:06 +0200 [thread overview]
Message-ID: <20130614055406.GA880@1wt.eu> (raw)
In-Reply-To: <1371183115.10688.78.camel@deadeye.wl.decadent.org.uk>
Hi Ben,
On Fri, Jun 14, 2013 at 05:11:55AM +0100, Ben Hutchings wrote:
> On Mon, 2013-06-10 at 12:15 +0200, Willy Tarreau wrote:
> [...]
> > Eric Dumazet (8):
> [...]
> > softirq: reduce latencies
> [...]
>
> This one apparently introduces a regression, fixed in mainline by commit
> 34376a50fb1f 'Fix lockup related to stop_machine being stuck in
> __do_softirq.'
>
> I'm a bit surprised that you picked it for 2.6.32 as it wasn't applied
> to any other branch older than 3.9.
Interesting. It was discussed on stable@ in March between Eric and Paul
about the pertinence of merging it into 2.6.32 and 2.6.34 (both CCed).
The thread was '[PATCH] net: reduce net_rx_action() latency to 2 HZ'.
It is supposed to fix a but introduced in 2.6.29 by commit 24f8b2385
(net: increase receive packet quantum).
I didn't notice that it was not in more recent versions.
Eric, do you suggest that I revert this patch or that I also include the
mainline fix above to fix the regression ? If the latter, should Paul and
Greg also take the two patches ?
Thanks,
Willy
prev parent reply other threads:[~2013-06-14 5:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 10:15 Linux 2.6.32.61 Willy Tarreau
2013-06-10 15:11 ` Sven-Haegar Koch
2013-06-10 16:04 ` Willy Tarreau
2013-06-13 17:53 ` Linux 2.6.32.61 - x86/ptrace/gcc 4.7 build error Willy Tarreau
2013-06-13 18:31 ` Sven-Haegar Koch
2013-06-13 18:41 ` Willy Tarreau
2013-06-14 6:23 ` Christoph Biedl
2013-06-14 6:36 ` Willy Tarreau
2013-06-14 4:11 ` Linux 2.6.32.61 Ben Hutchings
2013-06-14 5:54 ` Willy Tarreau [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130614055406.GA880@1wt.eu \
--to=w@1wt.eu \
--cc=ben@decadent.org.uk \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox