From: William Lee Irwin III <wli@holomorphy.com>
To: "M. Edward (Ed) Borasky" <znmeb@aracnet.com>
Cc: Andrew Morton <akpm@digeo.com>, Dave Hansen <haveblue@us.ibm.com>,
"Martin J. Bligh" <Martin.Bligh@us.ibm.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] add vmalloc stats to meminfo
Date: Sun, 15 Sep 2002 10:26:08 -0700 [thread overview]
Message-ID: <20020915172608.GJ3530@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0209151021530.3517-100000@shell1.aracnet.com>
On Sun, 15 Sep 2002, William Lee Irwin III wrote:
>> Also, dynamic vmalloc allocations may very well be starved by boot-time
>> allocations on systems where much vmallocspace is required for IO memory.
>> The failure mode of such is effectively deadlock, since they block
>> indefinitely waiting for permanent boot-time allocations to be freed up.
On Sun, Sep 15, 2002 at 10:23:24AM -0700, M. Edward (Ed) Borasky wrote:
> Thank you!! How difficult would it be to back-port this to 2.4.18?
Note the follow-up to this saying that the above paragraph was incorrect.
It doesn't sleep except to allocate backing memmory.
Bill
WARNING: multiple messages have this Message-ID (diff)
From: William Lee Irwin III <wli@holomorphy.com>
To: "M. Edward (Ed) Borasky" <znmeb@aracnet.com>
Cc: Andrew Morton <akpm@digeo.com>, Dave Hansen <haveblue@us.ibm.com>,
"Martin J. Bligh" <Martin.Bligh@us.ibm.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] add vmalloc stats to meminfo
Date: Sun, 15 Sep 2002 10:26:08 -0700 [thread overview]
Message-ID: <20020915172608.GJ3530@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0209151021530.3517-100000@shell1.aracnet.com>
On Sun, 15 Sep 2002, William Lee Irwin III wrote:
>> Also, dynamic vmalloc allocations may very well be starved by boot-time
>> allocations on systems where much vmallocspace is required for IO memory.
>> The failure mode of such is effectively deadlock, since they block
>> indefinitely waiting for permanent boot-time allocations to be freed up.
On Sun, Sep 15, 2002 at 10:23:24AM -0700, M. Edward (Ed) Borasky wrote:
> Thank you!! How difficult would it be to back-port this to 2.4.18?
Note the follow-up to this saying that the above paragraph was incorrect.
It doesn't sleep except to allocate backing memmory.
Bill
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-09-15 17:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-15 6:03 [PATCH] add vmalloc stats to meminfo Dave Hansen
2002-09-15 7:17 ` Andrew Morton
2002-09-15 7:17 ` Andrew Morton
2002-09-15 7:11 ` William Lee Irwin III
2002-09-15 7:11 ` William Lee Irwin III
2002-09-15 7:17 ` William Lee Irwin III
2002-09-15 7:17 ` William Lee Irwin III
2002-09-15 17:23 ` M. Edward (Ed) Borasky
2002-09-15 17:23 ` M. Edward (Ed) Borasky
2002-09-15 17:26 ` William Lee Irwin III [this message]
2002-09-15 17:26 ` William Lee Irwin III
2002-09-15 17:44 ` M. Edward Borasky
2002-09-15 17:44 ` M. Edward Borasky
2002-09-15 14:50 ` Martin J. Bligh
2002-09-15 14:50 ` Martin J. Bligh
2002-09-16 5:30 ` Matt Porter
2002-09-16 5:30 ` Matt Porter
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=20020915172608.GJ3530@holomorphy.com \
--to=wli@holomorphy.com \
--cc=Martin.Bligh@us.ibm.com \
--cc=akpm@digeo.com \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=znmeb@aracnet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.