From: arjan@fenrus.demon.nl
To: torvalds@transmeta.com (Linus Torvalds)
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.10-pre3 - bug report
Date: Sun, 2 Sep 2001 10:21:42 +0100 (BST) [thread overview]
Message-ID: <m15dTRm-000QCGC@amadeus.home.nl> (raw)
In-Reply-To: <200109020348.f823mCs01183@penguin.transmeta.com>
In article <200109020348.f823mCs01183@penguin.transmeta.com> you wrote:
> These are bounce buffer allocations - they do fail, but the failures
> should be temporary and the machine should make progress.
The patch I sent to linux-mm a week ago fixes this for "normal" loads.
It obviously doesn't fix the worst case scenario, but in the testing in the
Red Hat lab we've seen it 1) improve performance and 2) get rid of VM
problems caused by highmem; under normal load. Under the insane load we also
put our kernels on, it doesn't make much difference, the obvious deadlock is
still there.
Greetings,
Arjan van de Ven
prev parent reply other threads:[~2001-09-02 9:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-01 19:14 2.4.10-pre3 Linus Torvalds
2001-09-02 1:33 ` 2.4.10-pre3 - bug report Andrey Nekrasov
2001-09-02 3:48 ` Linus Torvalds
2001-09-02 9:21 ` arjan [this message]
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=m15dTRm-000QCGC@amadeus.home.nl \
--to=arjan@fenrus.demon.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®