From: "Peter T. Breuer" <ptb@it.uc3m.es>
To: Steve Whitehouse <Steve@ChyGwyn.com>
Cc: ptb@it.uc3m.es, Oliver Xymoron <oxymoron@waste.org>,
chen xiangping <chen_xiangping@emc.com>,
"'Jes Sorensen'" <jes@wildopensource.com>,
linux-kernel@vger.kernel.org
Subject: Re: Kernel deadlock using nbd over acenic driver.
Date: Fri, 17 May 2002 09:01:12 +0200 (MET DST) [thread overview]
Message-ID: <200205170701.g4H71CB25476@oboe.it.uc3m.es> (raw)
In-Reply-To: <200205161635.RAA26824@gw.chygwyn.com> from Steven Whitehouse at "May 16, 2002 05:35:43 pm"
"Steven Whitehouse wrote:"
> Thats effectively what PF_MEMALLOC does. The code in question is in
> page_alloc.c:__alloc_pages just before and after the rebalance: label.
> The z->pages_min gives a per zone minimum for "other processes" that are
> not PF_MEMALLOC,
A related question, then ... can one adjust the difference between the
ceiling for "normal" processes and PF_MEMALLOC processes, and if so,
how?
Peter
next prev parent reply other threads:[~2002-05-17 7:01 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-14 16:07 Kernel deadlock using nbd over acenic driver chen, xiangping
2002-05-14 16:32 ` Steven Whitehouse
2002-05-14 16:48 ` Alan Cox
2002-05-15 22:31 ` Oliver Xymoron
2002-05-16 5:10 ` Peter T. Breuer
2002-05-16 5:19 ` Peter T. Breuer
2002-05-16 14:29 ` Oliver Xymoron
2002-05-16 15:35 ` Peter T. Breuer
2002-05-16 16:22 ` Oliver Xymoron
2002-05-16 16:45 ` Peter T. Breuer
2002-05-16 16:35 ` Steven Whitehouse
2002-05-17 7:01 ` Peter T. Breuer [this message]
2002-05-17 9:26 ` Steven Whitehouse
-- strict thread matches above, loose matches on Subject: below --
2002-05-16 22:54 Peter T. Breuer
2002-05-17 8:44 ` Steven Whitehouse
2002-05-23 13:21 ` Peter T. Breuer
2002-05-24 10:11 ` Steven Whitehouse
2002-05-24 11:43 ` Peter T. Breuer
2002-05-24 13:28 ` Steven Whitehouse
2002-05-24 15:54 ` Peter T. Breuer
2002-05-27 13:04 ` Steven Whitehouse
2002-05-27 19:51 ` Peter T. Breuer
2002-05-27 13:44 ` Pavel Machek
2002-05-29 10:51 ` Peter T. Breuer
2002-05-29 11:21 ` Pavel Machek
2002-05-29 12:10 ` Peter T. Breuer
2002-05-29 13:24 ` Jens Axboe
2002-06-01 21:13 ` Peter T. Breuer
2002-06-05 8:48 ` Steven Whitehouse
2002-06-02 6:39 ` Pavel Machek
[not found] <3CE40A77.22C74DC1@zip.com.au>
2002-05-16 20:28 ` Peter T. Breuer
2002-05-16 13:18 chen, xiangping
2002-05-15 21:43 Peter T. Breuer
2002-05-16 8:33 ` Steven Whitehouse
2002-05-15 17:43 Peter T. Breuer
2002-05-15 19:43 ` Steven Whitehouse
2002-05-16 5:15 ` Peter T. Breuer
2002-05-16 8:04 ` Steven Whitehouse
2002-05-16 8:49 ` Peter T. Breuer
2002-05-15 16:01 Peter T. Breuer
2002-05-14 17:42 chen, xiangping
2002-05-14 17:36 chen, xiangping
2002-05-14 18:02 ` Alan Cox
2002-05-14 15:05 chen, xiangping
2002-05-14 15:11 ` Jes Sorensen
2002-05-10 15:39 chen, xiangping
2002-05-10 15:02 chen, xiangping
2002-05-10 15:11 ` Steven Whitehouse
2002-05-14 14:58 ` Jes Sorensen
2002-05-06 15:05 chen, xiangping
2002-05-07 8:15 ` Steven Whitehouse
2002-05-06 2:26 chen, xiangping
2002-05-06 8:45 ` Steven Whitehouse
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=200205170701.g4H71CB25476@oboe.it.uc3m.es \
--to=ptb@it.uc3m.es \
--cc=Steve@ChyGwyn.com \
--cc=chen_xiangping@emc.com \
--cc=jes@wildopensource.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oxymoron@waste.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).