linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.5.75
Date: 11 Jul 2003 01:30:36 +0200	[thread overview]
Message-ID: <1057879835.584.7.camel@teapot.felipe-alfaro.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0307101405490.4560-100000@home.osdl.org>

On Thu, 2003-07-10 at 23:14, Linus Torvalds wrote:
> Ok. This is it. We (Andrew and me) are going to start a "pre-2.6" series,
> where getting patches in is going to be a lot harder. This is the last
> 2.5.x kernel, so take note.

Is there any expected or planned timeframe to finalize the pre-2.6
series and end up with a stable 2.6.0 kernel?

I'm worried about the current status of the 2.5 kernel scheduler. I know
that Con is working hard to nail down all the problems that some people
like me are having. I don't still feel comfortable with it, and although
Con patches are several orders of magnitude better than stock scheduler,
there are minor problems.

Sometime ago, I made down a combo patch and, sincerely, it's the one I'm
using the most for my desktop boxes as it's the one that gets better
response times and interactive feeling. For my server boxes, neither my
combo patch, neither Con or stock do feel good when the system is under
heavy load. It suffers from starvation. Simply doing a "tar jxvf" makes
logging into the system a PITA.

Just my 2 cents.


  parent reply	other threads:[~2003-07-10 23:16 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-10 21:14 Linux 2.5.75 Linus Torvalds
2003-07-10 21:35 ` Russell King
2003-07-10 22:26   ` Linus Torvalds
2003-07-10 23:05     ` Russell King
2003-07-10 23:25       ` Linus Torvalds
2003-07-11 19:59       ` Horst von Brand
2003-07-10 23:30 ` Felipe Alfaro Solana [this message]
2003-07-10 23:38   ` Linus Torvalds
2003-07-10 23:46     ` Davide Libenzi
2003-07-10 23:40   ` Robert Love
2003-07-11  0:24     ` Diego Calleja García
2003-07-11  0:49       ` Wade
2003-07-11  7:09 ` Benjamin Herrenschmidt
2003-07-11 10:57 ` Linux 2.5.75 - still can't load aha152x (isapnp) => OOPS schmurtz
2003-07-11 17:53   ` Andrew Morton
2003-07-11 18:04     ` James Bottomley
2003-07-11 18:45     ` schmurtz
2003-07-11 12:30 ` incbin (was: Re: Linux 2.5.75) Geert Uytterhoeven
2003-07-11 12:32   ` Geert Uytterhoeven
2003-07-11 15:46 ` Linux 2.5.75 Oliver Pitzeier
2003-07-11 15:52 ` Linux 2.5.75 (compile statistics) John Cherry
2003-07-12 13:50 ` AMD 53C974 based SCSI adapter (was: Linux 2.5.75) Matthias Andree
     [not found] <20030710223548.A20214@flint.arm.linux.org.uk.suse.lists.linux.kernel>
     [not found] ` <Pine.LNX.4.44.0307101512350.4757-100000@home.osdl.org.suse.lists.linux.kernel>
2003-07-10 23:55   ` Linux 2.5.75 Andi Kleen
2003-07-11  0:12     ` Linus Torvalds
2003-07-11  0:55       ` Paul Mackerras
2003-07-11  8:42       ` Christoph Hellwig
2003-07-11 10:27         ` Lars Marowsky-Bree
2003-07-11 10:39           ` Christoph Hellwig
2003-07-11 16:52           ` Linus Torvalds
2003-07-11 17:03             ` Arjan van de Ven
2003-07-12 19:20               ` Horst von Brand
2003-07-12 23:17                 ` Jeff Garzik
     [not found] <7TEe.Bz.21@gated-at.bofh.it>
     [not found] ` <7TNS.Kc.9@gated-at.bofh.it>
2003-07-11 21:33   ` Arnd Bergmann

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=1057879835.584.7.camel@teapot.felipe-alfaro.com \
    --to=felipe_alfaro@linuxmail.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).