From: David Mosberger <davidm@napali.hpl.hp.com>
To: "Ulrich Weigand" <Ulrich.Weigand@de.ibm.com>
Cc: davidm@hpl.hp.com, Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] 4KB stack + irq stack for x86
Date: Thu, 6 Jun 2002 14:19:02 -0700 [thread overview]
Message-ID: <15615.53702.794957.958227@napali.hpl.hp.com> (raw)
In-Reply-To: <OF81A861D7.0F84A7BA-ONC1256BD0.0072344C@de.ibm.com>
>>>>> On Thu, 6 Jun 2002 22:55:12 +0200, "Ulrich Weigand" <Ulrich.Weigand@de.ibm.com> said:
Uli> So in the case of 8K page size, you need an order-2 allocation
Uli> for the stack, right? How do you handle failures due to
Uli> fragmentation?
We don't do anything special. I'm not sure what the fragmentation
statistics look like on machines with 1+GB memory; it's something I
have been wondering about and hoping to look into at some point (if
someone has done that already, I'd love to see the results). In
practice, every ia64 linux distro as of today ships with 16KB page
size, so you only get order-1 allocations for stacks.
--david
next prev parent reply other threads:[~2002-06-06 21:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 20:55 Ulrich Weigand
2002-06-06 21:19 ` David Mosberger [this message]
2002-06-06 22:10 ` Martin J. Bligh
2002-06-07 0:59 ` William Lee Irwin III
[not found] <OF70FD985F.A9C66B00-ONC1256BD0.0069C993@de.ibm.com.suse.lists.linux.kernel>
2002-06-06 19:49 ` Andi Kleen
2002-06-06 20:27 ` David Mosberger
2002-06-07 11:28 ` Maciej W. Rozycki
-- strict thread matches above, loose matches on Subject: below --
2002-06-06 19:24 Ulrich Weigand
[not found] <mailman.1023370621.16639.linux-kernel2news@redhat.com>
2002-06-06 17:37 ` Pete Zaitcev
2002-06-07 1:06 ` David S. Miller
2002-06-06 13:32 Ulrich Weigand
[not found] <20020604225539.F9111@redhat.com.suse.lists.linux.kernel>
[not found] ` <Pine.LNX.4.44.0206050820100.2941-100000@home.transmeta.com.suse.lists.linux.kernel>
[not found] ` <20020605144357.A4697@redhat.com.suse.lists.linux.kernel>
2002-06-05 20:40 ` Andi Kleen
2002-06-05 20:55 ` Linus Torvalds
2002-06-05 2:55 Benjamin LaHaise
2002-06-05 15:33 ` Linus Torvalds
2002-06-05 18:43 ` Benjamin LaHaise
2002-06-05 18:53 ` Linus Torvalds
2002-06-05 21:07 ` Benjamin LaHaise
2002-06-05 22:15 ` Steve Lord
2002-06-05 22:31 ` Benjamin LaHaise
2002-06-05 23:13 ` David S. Miller
2002-06-06 0:24 ` Larry McVoy
2002-06-06 1:15 ` Andi Kleen
2002-06-02 15:52 ` Pavel Machek
2002-06-09 18:50 ` Andi Kleen
2002-06-06 1:42 ` Benjamin LaHaise
2002-06-06 2:30 ` Stephen Lord
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=15615.53702.794957.958227@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=ak@suse.de \
--cc=davidm@hpl.hp.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®