public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Rik van Riel <riel@conectiva.com.br>,
	Ben LaHaise <bcrl@redhat.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: Linux-2.4.5
Date: Sat, 26 May 2001 17:38:47 +0200	[thread overview]
Message-ID: <20010526173847.C9634@athlon.random> (raw)
In-Reply-To: <20010526171459.Y9634@athlon.random> <Pine.LNX.4.21.0105260818150.3684-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.21.0105260818150.3684-100000@penguin.transmeta.com>; from torvalds@transmeta.com on Sat, May 26, 2001 at 08:23:00AM -0700

On Sat, May 26, 2001 at 08:23:00AM -0700, Linus Torvalds wrote:
> 
> On Sat, 26 May 2001, Andrea Arcangeli wrote:
> > 
> > I don't see where you fixed the deadlock in create_buffers, if you did
> > please show me which line of code is supposed to do that, I show you
> > below which lines of code in my patch should fix the wait_event deadlock
> > in create_buffers:
> 
> Andrea, look at the page_alloc() path, and the "don't loop forever if
> __GFP_IO isn't set and we're not making progress". That looks entirely
> sane.

yes, I was only talking about create_buffers, not __alloc_pages. That
patch can certainly address problems in alloc_pages.

> (and I like your patch that removes some more magic limits - I suspect the
> proper fix is the 5 lines from Rik's patch in page_alloc.c, and your patch
> together - amybody mind testing that out?)

Sounds the same to me.

> Oh, and I still _do_ think that we should rename the silly "async" flag as
> "can_do_io", and then use that to determine whether to do SLAB_KERNEL or
> SLAB_BUFFER. That would make more things able to do IO, which in turn
> should help balance things out.

getblk still needs to use SLAB_BUFFER, not sure how many callers will be
allowed to use SLAB_KERNEL, but certainly the "async" name was not very
appropriate to indicate if the bh allocation can fail or not.

Andrea

  parent reply	other threads:[~2001-05-26 15:39 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010526171459.Y9634@athlon.random>
2001-05-26 15:22 ` Linux-2.4.5 Rik van Riel
2001-05-26 15:30   ` Linux-2.4.5 Andrea Arcangeli
2001-05-26 15:51     ` Linux-2.4.5 Rik van Riel
2001-05-26 16:04       ` Linux-2.4.5 Andrea Arcangeli
2001-05-26 15:23 ` Linux-2.4.5 Linus Torvalds
2001-05-26 15:31   ` Linux-2.4.5 Rik van Riel
2001-05-26 15:38   ` Andrea Arcangeli [this message]
2001-05-26 16:03     ` Linux-2.4.5 Linus Torvalds
2001-05-26 18:11 ` Linux-2.4.5 Ben LaHaise
2001-05-26 18:31   ` Linux-2.4.5 Andrea Arcangeli
2001-05-26 19:42     ` Linux-2.4.5 Ingo Molnar
2001-05-26 19:56       ` Linux-2.4.5 Andrea Arcangeli
2001-05-26  0:34 [with-PATCH-really] highmem deadlock removal, balancing & cleanup Linus Torvalds
2001-05-26  1:28 ` Linux-2.4.5 Linus Torvalds
2001-05-26  1:35   ` Linux-2.4.5 Rik van Riel
2001-05-26  1:39   ` Linux-2.4.5 Ben LaHaise
2001-05-26  1:59     ` Linux-2.4.5 Andrea Arcangeli
2001-05-26  2:11       ` Linux-2.4.5 Ben LaHaise
2001-05-26  2:38         ` Linux-2.4.5 Andrea Arcangeli
2001-05-26  2:49           ` Linux-2.4.5 Ben LaHaise
2001-05-26  3:11             ` Linux-2.4.5 Andrea Arcangeli
2001-05-26  4:22               ` Linux-2.4.5 Linus Torvalds
2001-05-26  4:31                 ` Linux-2.4.5 Rik van Riel
2001-05-26  8:10                   ` Linux-2.4.5 Linus Torvalds
2001-05-26  9:01                     ` Linux-2.4.5 Linus Torvalds
2001-05-26  9:18                 ` Linux-2.4.5 arjan
2001-05-26 14:18                 ` Linux-2.4.5 Andrea Arcangeli
2001-05-26 14:21                   ` Linux-2.4.5 Rik van Riel
2001-05-26 14:38                     ` Linux-2.4.5 Andrea Arcangeli
2001-05-26 14:40                       ` Linux-2.4.5 Rik van Riel
2001-05-26 15:17                         ` Linux-2.4.5 Linus Torvalds
2001-05-26 15:28                           ` Linux-2.4.5 Rik van Riel
2001-05-26 15:59                             ` Linux-2.4.5 Linus Torvalds
2001-05-26 22:12                               ` Linux-2.4.5 Marcelo Tosatti
2001-05-27  6:53                                 ` Linux-2.4.5 Marcelo Tosatti
2001-06-03 23:32                                   ` Linux-2.4.5 Linus Torvalds
2001-06-05  2:21                                     ` Linux-2.4.5 Marcelo Tosatti
2001-05-26 15:09                     ` Linux-2.4.5 Linus Torvalds
2001-05-26 15:18                       ` Linux-2.4.5 Rik van Riel
2001-05-26 15:24                         ` Linux-2.4.5 Andrea Arcangeli
2001-05-26 15:26                           ` Linux-2.4.5 Rik van Riel
2001-05-26 15:40                             ` Linux-2.4.5 Andrea Arcangeli
2001-05-26  4:45               ` Linux-2.4.5 Rik van Riel
2001-05-26  4:47                 ` Linux-2.4.5 Rik van Riel
2001-05-26  6:07                   ` Linux-2.4.5 Ben LaHaise
2001-05-26 14:32                 ` Linux-2.4.5 Andrea Arcangeli
2001-05-26 14:36                   ` Linux-2.4.5 Rik van Riel
2001-05-26 15:03                     ` Linux-2.4.5 Andrea Arcangeli
2001-05-26 15:08                       ` Linux-2.4.5 Rik van Riel
2001-05-26 15:20                         ` Linux-2.4.5 Andrea Arcangeli
2001-05-26 15:41         ` Linux-2.4.5 Rik van Riel

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=20010526173847.C9634@athlon.random \
    --to=andrea@suse.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bcrl@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    --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