From: "Jason Munro" <jason@stdbev.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.8-rc3-np1
Date: Tue, 10 Aug 2004 12:31:55 -0500 [thread overview]
Message-ID: <bec7be7a859af61df0afc46dd7220232@stdbev.com> (raw)
In-Reply-To: <4117494E.704@yahoo.com.au>
On 4:52:14 am 08/09/04 Nick Piggin <nickpiggin@yahoo.com.au> wrote:
> http://www.kerneltrap.org/~npiggin/2.6.8-rc3-np1/
>
> Patch is against 2.6.8-rc3-mm2 only at this stage due to significant
> memory management changes in there making it difficult to track Linus'
> tree as well.
>
> Feedback on the scheduler would be much appreciated, as it might get
> a run in Andrew's tree soon.
>
Running great on my Toshiba laptop. No benchmark numbers but I played some
DVDs, ogg files, emerged some pacakges. All very smooth.
\__ Jason Munro
\__ jason@stdbev.com
\__ http://hastymail.sourceforge.net/
next prev parent reply other threads:[~2004-08-10 17:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 9:52 2.6.8-rc3-np1 Nick Piggin
2004-08-10 17:31 ` Jason Munro [this message]
2004-08-11 22:13 ` 2.6.8-rc3-np1 Martin Schlemmer
2004-08-11 23:04 ` 2.6.8-rc3-np1 Matt Heler
2004-08-12 4:42 ` 2.6.8-rc3-np1 Martin Schlemmer
2004-08-12 7:11 ` 2.6.8-rc3-np1 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=bec7be7a859af61df0afc46dd7220232@stdbev.com \
--to=jason@stdbev.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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