All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Larson <plars@linuxtestproject.org>
To: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
Cc: Andrew Morton <akpm@digeo.com>,
	lkml <linux-kernel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>
Subject: Re: 2.5.69-mm8
Date: 22 May 2003 14:30:41 -0500	[thread overview]
Message-ID: <1053631843.2648.3248.camel@plars> (raw)
In-Reply-To: <1053629620.596.1.camel@teapot.felipe-alfaro.com>

[-- Attachment #1: Type: text/plain, Size: 967 bytes --]

On Thu, 2003-05-22 at 13:53, Felipe Alfaro Solana wrote:
> On Thu, 2003-05-22 at 11:16, Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.69/2.5.69-mm8/
> > 
> > . One anticipatory scheduler patch, but it's a big one.  I have not stress
> >   tested it a lot.  If it explodes please report it and then boot with
> >   elevator=deadline.
> > 
> > . The slab magazine layer code is in its hopefully-final state.
> > 
> > . Some VFS locking scalability work - stress testing of this would be
> >   useful.
> 
> Running on it right now... Compiles and boots. I'm sure it won't explode
> on my face :-)
2.5.69-mm8 is bleeding for me. :)  See bugs #738 and #739.  I don't
*think* they are the same but apologies in advance if they are.  #738
appears to have been produced mostly by running LTP and #739 I got with
a combination of ftest07 and aio01 from LTP and previously just by
compiling LTP.

-Paul Larson

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 240 bytes --]

  reply	other threads:[~2003-05-22 19:17 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-22  9:16 2.5.69-mm8 Andrew Morton
2003-05-22  9:16 ` 2.5.69-mm8 Andrew Morton
2003-05-22 12:05 ` 2.5.69-mm8 Philippe Gramoullé
2003-05-22 12:05   ` 2.5.69-mm8 Philippe Gramoullé
2003-05-22 12:07 ` 2.5.69-mm8 Helge Hafting
2003-05-22 12:07   ` 2.5.69-mm8 Helge Hafting
2003-05-22 21:21   ` 2.5.69-mm8 Rudmer van Dijk
2003-05-22 21:21     ` 2.5.69-mm8 Rudmer van Dijk
2003-05-22 14:55 ` 2.5.69-mm8 William Lee Irwin III
2003-05-22 14:55   ` 2.5.69-mm8 William Lee Irwin III
2003-05-22 17:13 ` 2.5.69-mm8 Alexander Hoogerhuis
2003-05-22 17:13   ` 2.5.69-mm8 Alexander Hoogerhuis
2003-05-22 18:53 ` 2.5.69-mm8 Felipe Alfaro Solana
2003-05-22 18:53   ` 2.5.69-mm8 Felipe Alfaro Solana
2003-05-22 19:30   ` Paul Larson [this message]
2003-05-22 19:39     ` 2.5.69-mm8 Martin J. Bligh
2003-05-22 19:39       ` 2.5.69-mm8 Martin J. Bligh
2003-05-22 19:49       ` 2.5.69-mm8 Paul Larson
2003-05-22 21:03       ` 2.5.69-mm8 Dave Hansen
2003-05-22 21:03         ` 2.5.69-mm8 Dave Hansen
2003-05-22 20:14     ` 2.5.69-mm8 Andrew Morton
2003-05-22 20:14       ` 2.5.69-mm8 Andrew Morton
2003-05-22 21:19       ` 2.5.69-mm8 Paul Larson
2003-05-23  6:18 ` 2.5.69-mm8 Martin J. Bligh
2003-05-23  6:18   ` 2.5.69-mm8 Martin J. Bligh
2003-05-23  7:03   ` 2.5.69-mm8 Dave Hansen
2003-05-23  7:03     ` 2.5.69-mm8 Dave Hansen
2003-05-23 14:32     ` 2.5.69-mm8 Martin J. Bligh
2003-05-23 14:32       ` 2.5.69-mm8 Martin J. Bligh
2003-05-23 15:02       ` 2.5.69-mm8 William Lee Irwin III
2003-05-23 15:02         ` 2.5.69-mm8 William Lee Irwin III
2003-05-23 15:31   ` 2.5.69-mm8 Martin J. Bligh
2003-05-23 15:31     ` 2.5.69-mm8 Martin J. Bligh
2003-05-23 17:23 ` 2.5.69-mm8 Arador

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=1053631843.2648.3248.camel@plars \
    --to=plars@linuxtestproject.org \
    --cc=akpm@digeo.com \
    --cc=felipe_alfaro@linuxmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.