public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: Tim Schmielau <tim@physik3.uni-rostock.de>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 64 bit jiffies for 2.4.23-pre2
Date: Mon, 1 Sep 2003 21:02:10 +0200	[thread overview]
Message-ID: <20030901190210.GA24145@alpha.home.local> (raw)
In-Reply-To: <Pine.LNX.4.33.0309012024320.26435-100000@gans.physik3.uni-rostock.de>

On Mon, Sep 01, 2003 at 08:28:31PM +0200, Tim Schmielau wrote:
> On Mon, 1 Sep 2003, Marcelo Tosatti wrote:
> 
> > > I think it's the most appropriate solution for 2.4. But you need to decide
> > > whether you take this, whether someone should backport the (intrusive and
> > > architecture-dependent) 2.6 fix, or whether you drop it completly and let
> > > people just upgrade to 2.6.
> >
> > Sincerely, I prefer people use 2.6.
> 
> OK, for people wanting this in their private trees, I'll try to keep an
> up-to-date version at
> 
>   http://www.physik3.uni-rostock.de/tim/kernel/2.4/

Ok, thanks Tim, I'll keep including it in my kernel since it allows my systems
to live such a long life :-) But I don't think they will ever beat Alan's box
which lasted 1100 days on 1.2.13 ! And that would not be reasonable because
even for security reasons, you sometimes have to upgrade.

BTW, that reminds me of Netware's patches that were basically hot fixes that
you could apply without shutting the system down. That was really wonderful a
feature that I would love to see on Linux. This is already doable with modules,
but not with the system core.

Regards,
Willy


  reply	other threads:[~2003-09-01 19:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-31 11:16 [PATCH] 64 bit jiffies for 2.4.23-pre2 Tim Schmielau
2003-09-01 18:10 ` Marcelo Tosatti
2003-09-01 18:28   ` Tim Schmielau
2003-09-01 19:02     ` Willy Tarreau [this message]
2003-09-03 18:43       ` bill davidsen

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=20030901190210.GA24145@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tim@physik3.uni-rostock.de \
    /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