All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Olivier Croquette <ocroquette@free.fr>,
	Andrew Morton <akpm@osdl.org>,
	torvalds@osdl.org
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: setitimer expire too early (Kernel 2.4)
Date: Thu, 30 Jun 2005 13:50:53 -0300	[thread overview]
Message-ID: <20050630165053.GA8220@logos.cnet> (raw)
In-Reply-To: <42C444AA.2070508@free.fr>

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?
> 
> 2. I downloaded the full 2.4.31 source code. The patch appears not to be 
> included. Where/Who should I signal that?

And what about the side effects:
This however will produce pathological cases, like having a idle system
being requested 1 ms timeouts will give systematically 2 ms timeouts,
whereas currently it simply gives a few usecs less than 1 ms. 

Linus, Andrew, do you consider this critical enough to be merged to 
the v2.4 tree?

  reply	other threads:[~2005-06-30 21:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-30 19:14 setitimer expire too early (Kernel 2.4) Olivier Croquette
2005-06-30 16:50 ` Marcelo Tosatti [this message]
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

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=20050630165053.GA8220@logos.cnet \
    --to=marcelo.tosatti@cyclades.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ocroquette@free.fr \
    --cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.