public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Robert Macaulay <robert_macaulay@dell.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	Rik van Riel <riel@conectiva.com.br>,
	Craig Kulesa <ckulesa@as.arizona.edu>,
	linux-kernel@vger.kernel.org, Bob Matthews <bmatthews@redhat.com>,
	Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: highmem deadlock fix [was Re: VM in 2.4.10(+tweaks) vs. 2.4.9-ac14/15(+stuff)]
Date: Fri, 28 Sep 2001 04:24:17 +0200	[thread overview]
Message-ID: <20010928042417.J14277@athlon.random> (raw)
In-Reply-To: <20010928014720.Z14277@athlon.random> <Pine.LNX.4.33.0109272108400.29056-100000@ping.us.dell.com>
In-Reply-To: <Pine.LNX.4.33.0109272108400.29056-100000@ping.us.dell.com>; from robert_macaulay@dell.com on Thu, Sep 27, 2001 at 09:12:25PM -0500

On Thu, Sep 27, 2001 at 09:12:25PM -0500, Robert Macaulay wrote:
> Thanks Andrea. I'll see if we can repeat the 0-page alloc again.

Ok, it is possible the 0-page alloc failed because NOHIGHIO was
disabled, Linus's fix being less finegrined than mine could also lead
more easily to 0-page alloc failed.

However failing bounce-allocation is not important since we have the
reserved pool for those allocations. Not having to use the reserved
pool only allows an higher amount of I/O in parallel. This is why I said
we could have dropped the NOHIGHIO logic in first place if we wanted to
go the non finegrined way.

Andrea

  reply	other threads:[~2001-09-28  2:24 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-26 13:38 VM in 2.4.10(+tweaks) vs. 2.4.9-ac14/15(+stuff) Craig Kulesa
2001-09-26 14:03 ` Andrea Arcangeli
2001-09-26 14:23   ` Rik van Riel
2001-09-26 14:49     ` Andrea Arcangeli
2001-09-26 18:17       ` Robert Macaulay
2001-09-26 18:36         ` Andrea Arcangeli
2001-09-27 22:13           ` highmem deadlock fix [was Re: VM in 2.4.10(+tweaks) vs. 2.4.9-ac14/15(+stuff)] Andrea Arcangeli
2001-09-27 22:55             ` J . A . Magallon
2001-09-27 23:16             ` Linus Torvalds
2001-09-27 23:18               ` Linus Torvalds
2001-09-27 23:37                 ` Andrea Arcangeli
2001-09-27 23:51                   ` Rik van Riel
2001-09-28  1:26                     ` Andrea Arcangeli
2001-09-28  1:28                     ` Linus Torvalds
2001-09-27 23:47               ` Andrea Arcangeli
2001-09-28  0:03                 ` Linus Torvalds
2001-09-28  0:11                   ` Andrea Arcangeli
2001-09-28  2:12                 ` Robert Macaulay
2001-09-28  2:24                   ` Andrea Arcangeli [this message]
2001-09-28 13:36                     ` Robert Macaulay
2001-09-28 14:02                     ` LILO causes segmentation fault and panic [was Re: highmem deadlock fix] Robert Macaulay
2001-09-28  0:08               ` highmem deadlock fix [was Re: VM in 2.4.10(+tweaks) vs. 2.4.9-ac14/15(+stuff)] Andrea Arcangeli

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=20010928042417.J14277@athlon.random \
    --to=andrea@suse.de \
    --cc=bmatthews@redhat.com \
    --cc=ckulesa@as.arizona.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=riel@conectiva.com.br \
    --cc=robert_macaulay@dell.com \
    --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