public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: Jean Tourrilhes <jt@hpl.hp.com>,
	Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.4] Wireless Extension v17 (resend)
Date: Tue, 8 Feb 2005 23:45:31 +0100	[thread overview]
Message-ID: <20050208224531.GE1850@alpha.home.local> (raw)
In-Reply-To: <20050208184145.GD10799@logos.cnet>

Hi Marcelo,

On Tue, Feb 08, 2005 at 04:41:46PM -0200, Marcelo Tosatti wrote:
> > 
> > 	There need to be some unique features in 2.6.X to force people
> > to upgrade, I guess...
> 
> Faster, cleaner, way more elegant, handles intense loads more gracefully, 

When a CPU-hungry task freezes another one for more than 13 seconds, I cannot
agree with your last statement, and that's why I still don't upgrade. I have
already posted examples of worst case scenarios, but I now start to have a
more meaningful example to show so that people working on the scheduler may
have something clearer to work with. I also did not have time to retest -ck
or staircase recently, but I will do for completeness.

> handles highmem decently, LSM/SELinux, etc, etc...
> 
> IMO everyone should upgrade whenever appropriate. 

I still know about a tens of 2.2 still running around at customers ;-)
However, if it had not been for lazyness, they should have upgraded.

Cheers,
Willy


  reply	other threads:[~2005-02-08 22:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-08 18:16 [PATCH 2.4] Wireless Extension v17 (resend) Jean Tourrilhes
2005-02-08 18:01 ` Marcelo Tosatti
2005-02-08 21:51   ` Jean Tourrilhes
2005-02-08 18:41     ` Marcelo Tosatti
2005-02-08 22:45       ` Willy Tarreau [this message]
2005-02-08 20:05         ` Marcelo Tosatti
2005-02-09  0:37       ` Jean Tourrilhes
2005-02-09  1:51         ` Chris Wright
2005-02-09  2:07           ` Jean Tourrilhes
2005-02-09  2:17             ` Chris Wright
2005-02-09  1:09       ` kernel
2005-02-08 22:28         ` Marcelo Tosatti
2005-02-09  1:21         ` kernel

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=20050208224531.GE1850@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=jt@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    /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