public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oliver Neukum <oliver@neukum.org>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Hugh Dickins <hugh@veritas.com>,
	Pete Zaitcev <zaitcev@redhat.com>,
	Arjan van de Ven <arjanv@redhat.com>, Alan Cox <alan@redhat.com>,
	Greg KH <greg@kroah.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Rik van Riel <riel@redhat.com>
Subject: Re: PF_MEMALLOC in 2.6
Date: Fri, 20 Aug 2004 17:34:10 +0200	[thread overview]
Message-ID: <200408201734.10317.oliver@neukum.org> (raw)
In-Reply-To: <1092997872.1996.51.camel@sisko.scot.redhat.com>

Am Freitag, 20. August 2004 12:31 schrieb Stephen C. Tweedie:
> Hi,
> 
> On Thu, 2004-08-19 at 13:41, Hugh Dickins wrote:
> 
> > Or would it solve the problem at hand, if it made itself PF_MEMALLOC
> > just while servicing a request from a PF_MEMALLOC?
> 
> It's not the PF_* state of the caller who submitted the IO that matters,
> though --- it's the state of all threads _waiting_ on the IO, which may
> be different, and which can change even after the IO has begun.  
> 
> Eg. kswapd does a writepage, the writepage needs to allocate disk space,
> and in doing so tries to access a metadata block which is already
> undergoing IO from a different thread altogether.

Then how do the current SCSI drivers work?

	Regards
			Oliver

      reply	other threads:[~2004-08-20 15:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-19  6:55 PF_MEMALLOC in 2.6 Pete Zaitcev
2004-08-19  6:59 ` William Lee Irwin III
2004-08-19  8:46 ` Stephen C. Tweedie
2004-08-19  8:59 ` Oliver Neukum
2004-08-19 12:41 ` Hugh Dickins
2004-08-19 18:25   ` Oliver Neukum
2004-08-20  2:37     ` Nick Piggin
2004-08-20  7:56       ` Oliver Neukum
2004-08-20  8:06         ` Nick Piggin
2004-08-20  8:40           ` Pete Zaitcev
2004-08-20 14:50             ` Oliver Neukum
2004-08-20 15:02               ` Alan Cox
2004-08-20 16:04                 ` Rik van Riel
2004-08-20 16:06                   ` Arjan van de Ven
2004-08-20 16:10                     ` Alan Cox
2004-08-20 16:14                       ` Rik van Riel
2004-08-21  2:03                 ` Nick Piggin
2004-08-20  8:52           ` Oliver Neukum
2004-08-20  9:06             ` Nick Piggin
2004-08-26 21:16             ` Zephaniah E. Hull
2004-08-26 22:04               ` Oliver Neukum
     [not found]                 ` <20040827032554.GB30820@babylon.d2dc.net>
2004-08-27  9:15                   ` Oliver Neukum
2004-08-26 23:41               ` Mikulas Patocka
2004-08-20 10:31   ` Stephen C. Tweedie
2004-08-20 15:34     ` Oliver Neukum [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=200408201734.10317.oliver@neukum.org \
    --to=oliver@neukum.org \
    --cc=alan@redhat.com \
    --cc=arjanv@redhat.com \
    --cc=greg@kroah.com \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@redhat.com \
    --cc=sct@redhat.com \
    --cc=zaitcev@redhat.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