From: Willy Tarreau <willy@w.ods.org>
To: Olivier Croquette <ocroquette@free.fr>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: setitimer expire too early (Kernel 2.4)
Date: Thu, 30 Jun 2005 23:46:42 +0200 [thread overview]
Message-ID: <20050630214642.GK8907@alpha.home.local> (raw)
In-Reply-To: <42C444AA.2070508@free.fr>
Hello Olivier,
On Thu, Jun 30, 2005 at 09:14:50PM +0200, Olivier Croquette wrote:
>
> I am refering to this bug:
>
> http://bugzilla.kernel.org/show_bug.cgi?id=4569
>
> A thread led to a patch from Paulo:
>
> http://kerneltrap.org/mailarchive/1/message/59454/flat
>
> This patch has been included in the kernel 2.6.12.
>
> 1. How can I easily check if the patch is planned for include in the 2.4?
Right now, simply by asking Marcelo. As he's moving his tree from BK to
git, I suspect we'll not see any intermediate merge before 2.4.32-pre1.
> 2. I downloaded the full 2.4.31 source code. The patch appears not to be
> included. Where/Who should I signal that?
Here is a good place. Unfortunately, the thread pointed above ended
quickly, and it does not seem clear from this whether Paulo's patch
should be applied or not, as adding 1 jiffie at 100 Hz will result in
a (noticeable) 10 ms additionnal sleep time. If you know of applications
which break because of this problem, and there is a general consensus
stating that the patch will not break anything, I can issue a 2.4.31-hf1,
but it does not seem critical enough to justify a hotfix.
Regards,
Willy
prev parent reply other threads:[~2005-06-30 21:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-30 19:14 Olivier Croquette
2005-06-30 16:50 ` Marcelo Tosatti
2005-06-30 21:59 ` Willy Tarreau
2005-06-30 23:05 ` Andrew Morton
2005-07-01 9:44 ` George Anzinger
2005-07-01 17:52 ` Olivier Croquette
2005-07-01 14:49 ` Marcelo Tosatti
2005-07-01 21:14 ` George Anzinger
2005-07-03 11:56 ` Marcelo Tosatti
2005-07-04 11:47 ` Marcelo Tosatti
2005-06-30 21:46 ` 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=20050630214642.GK8907@alpha.home.local \
--to=willy@w.ods.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ocroquette@free.fr \
/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
all inboxes | Powered by JetHome®