From: Ed Tomlinson <tomlins@cam.org>
To: Andrew Morton <akpm@digeo.com>,
Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.64-mm7
Date: Sat, 15 Mar 2003 08:36:37 -0500 [thread overview]
Message-ID: <200303150836.38150.tomlins@cam.org> (raw)
In-Reply-To: <20030315033550.32bc34cd.akpm@digeo.com>
On March 15, 2003 06:35 am, Andrew Morton wrote:
> "Felipe Alfaro Solana" <felipe_alfaro@linuxmail.org> wrote:
> > ----- Original Message -----
> > From: Andrew Morton <akpm@digeo.com>
> > Date: Sat, 15 Mar 2003 01:17:58 -0800
> > To: linux-kernel@vger.kernel.org, linux-mm@kvack.org
> > Subject: 2.5.64-mm7
> >
> > > . Niggling bugs in the anticipatory scheduler are causing problems.
> > > I've reset the default to elevator=deadline until we get these fixed
> > > up.
> >
> > I haven't still experienced those bugs using mm6 and AS.
>
> Me either.
>
> > Is there an easy way to reproduce them?
>
> If there was, they'd be fixed.
Actually its easy to repro at least one of them here. Nick has
been sending me debug versions of the patch and has a debug output
from a boot here that stalls. IMHO Latench is as big a problem
as reproducing the bug(s).
Ed Tomlinson
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
next prev parent reply other threads:[~2003-03-15 13:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-15 11:29 2.5.64-mm7 Felipe Alfaro Solana
2003-03-15 11:35 ` 2.5.64-mm7 Andrew Morton
2003-03-15 13:36 ` Ed Tomlinson [this message]
2003-03-15 17:01 ` 2.5.64-mm7 Arador
-- strict thread matches above, loose matches on Subject: below --
2003-03-15 9:17 2.5.64-mm7 Andrew Morton
2003-03-15 10:13 ` 2.5.64-mm7 Russell King
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=200303150836.38150.tomlins@cam.org \
--to=tomlins@cam.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox