From: Ed Tomlinson <tomlins@cam.org>
To: linux-kernel@vger.kernel.org
Cc: alan@lxorguk.ukuu.org.uk
Subject: [lkml]Re: VM problems still in 2.2.18
Date: Fri, 15 Dec 2000 08:00:44 -0500 [thread overview]
Message-ID: <00121508004400.16895@oscar> (raw)
Alan Cox wrote:
> > slrnpull --expire on a news-spool of about 600 Mb in 200,000 files gave
> > a lot of 'trying_to_free..' errors.
> >
> > 2.2.18 + VM-global, booted with mem=32M:
> >
> > slrnpull --expire on the same spool worked fine.
>
> I think Andrea just earned his official God status ;)
I have been using the aa series kernels through out the 18pre series (with
reiserfs). They have worked very well. Suggest you and Andrea talk and
figure out what else from this series can be put into 19pre. Believe the
major changes left in the aa series are bigmem and lvm. I would love to see
lvm officially in 2.2...
Luck,
Ed Tomlinson
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-12-15 13:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-15 13:00 Ed Tomlinson [this message]
2000-12-15 17:52 ` [lkml]Re: VM problems still in 2.2.18 Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2000-12-14 2:36 Mark Symonds
2000-12-14 9:57 ` Alan Cox
2000-12-14 20:09 ` [lkml]Re: " thunder7
2000-12-14 22:38 ` Alan Cox
2000-12-14 22:39 ` J Sloan
2000-12-14 23:17 ` Alan Cox
2000-12-15 14:29 ` Andrea Arcangeli
2000-12-15 17:57 ` Alan Cox
2000-12-15 18:22 ` Andrea Arcangeli
2000-12-15 18:46 ` Alan Cox
2000-12-15 19:09 ` Andrea Arcangeli
2000-12-15 19:17 ` Alan Cox
2000-12-16 10:49 ` Chris Mason
2000-12-16 13:39 ` Andrea Arcangeli
2000-12-14 23:12 ` J . A . Magallon
2000-12-18 1:03 ` Mark Symonds
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=00121508004400.16895@oscar \
--to=tomlins@cam.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.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.