From: Roberto Sanchez <rcsanchez97@yahoo.es>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.6.1-mm3
Date: Wed, 14 Jan 2004 20:47:20 -0500 [thread overview]
Message-ID: <4005F128.3080208@yahoo.es> (raw)
In-Reply-To: <20040114014846.78e1a31b.akpm@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 979 bytes --]
Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.1/2.6.1-mm3/
>
>
> - A big ppc64 update from Anton
>
> - Added Nick's CPU scheduler patches for hyperthreaded/SMT CPUs. This work
> needs lots of testing and review from those who care about and work upon
> this feature, please.
>
> - An I/O scheduler tuning patch. This is the 114th patch against the
> anticipatory scheduler and we're nearly finished, honest. Now would be a
> good time for people to run the appropriate benchmarks.
>
> We're still not as good as deadline on some seeky loads, and deep SCSI
> TCQ still hurts a lot. But it is looking good on average.
>
> - Plenty of other random stuff
I am still getting lock-ups on my system (nForce2 w/ Athlon XP 2500+).
I am currently stuck at 2.6.1-rc1-mm1. If there is anything I can do
to help track down the problem I would be happy to help, I just need
some pointers on where to start.
-Roberto Sanchez
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2004-01-15 1:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 9:48 2.6.1-mm3 Andrew Morton
2004-01-14 12:27 ` 2.6.1-mm3 Jes Sorensen
2004-01-14 13:06 ` 2.6.1-mm3 Dmitry Torokhov
2004-01-14 16:04 ` 2.6.1-mm3 (compile stats) John Cherry
2004-01-14 19:11 ` 2.6.1-mm3 Thomas Schlichter
2004-01-14 19:11 ` 2.6.1-mm3 Thomas Schlichter
2004-01-14 19:12 ` 2.6.1-mm3 Thomas Schlichter
2004-01-14 19:12 ` 2.6.1-mm3 Thomas Schlichter
2004-01-14 19:12 ` 2.6.1-mm3 Thomas Schlichter
2004-01-15 1:47 ` Roberto Sanchez [this message]
2004-01-15 2:39 ` 2.6.1-mm3 Nick Piggin
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=4005F128.3080208@yahoo.es \
--to=rcsanchez97@yahoo.es \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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