From: Chuck Ebbert <cebbert@redhat.com>
To: Bill Irwin <bill.irwin@oracle.com>,
Chuck Ebbert <cebbert@redhat.com>,
linux-kernel@vger.kernel.org, bunk@stusta.de, akpm@osdl.org,
gcoady@gmail.com, zlynx@acm.org, dgc@sgi.com,
alan@lxorguk.ukuu.org.uk, andi@firstfloor.org, hch@infradead.org,
jengelh@linux01.gwdg.de, zwane@infradead.org, neilb@suse.de,
jens.axboe@oracle.com, eric@provenscaling.com
Subject: Re: [3/3] use vmalloc() to arrange guard pages for stacks
Date: Tue, 01 May 2007 12:40:55 -0400 [thread overview]
Message-ID: <46376D97.3040603@redhat.com> (raw)
In-Reply-To: <20070501163140.GM26598@holomorphy.com>
Bill Irwin wrote:
>
> It's a shame that the resource scalability implications of vmallocspace
> allocations prevent this from being useful in production. One could, in
> principle, establish guard pages within ZONE_NORMAL, but for 4KB stacks
> it's somewhat awkward to dredge up 3 contigous pages, and 4 defeats the
> purpose. Alignment with 8KB stacks wants 2 contiguous order 1 pages that
> span an order 2 page boundary. I guess I could rewrite the page allocator
> (again), but people seem to feel safest with the buddy allocator affairs.
>
> BTW, did the original patches for this prove to be of any use to you?
>
No, I never tried them. Seems like I never get to anything these days but
answering bug reports and merging fixes... Putting the feature in-kernel
means I might get to use it though. :)
next prev parent reply other threads:[~2007-05-01 16:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 23:23 [0/3] i386 stack handling updates Bill Irwin
2007-04-30 23:33 ` [1/3] dynamically allocate IRQ stacks Bill Irwin
2007-04-30 23:37 ` [2/3] unconditional i386 " Bill Irwin
2007-04-30 23:40 ` [3/3] use vmalloc() to arrange guard pages for stacks Bill Irwin
2007-05-01 15:07 ` Chuck Ebbert
2007-05-01 16:31 ` Bill Irwin
2007-05-01 16:40 ` Chuck Ebbert [this message]
2007-05-01 16:47 ` Bill Irwin
2007-05-01 17:04 ` [1/3] dynamically allocate IRQ stacks Heiko Carstens
2007-05-01 17:26 ` Bill Irwin
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=46376D97.3040603@redhat.com \
--to=cebbert@redhat.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andi@firstfloor.org \
--cc=bill.irwin@oracle.com \
--cc=bunk@stusta.de \
--cc=dgc@sgi.com \
--cc=eric@provenscaling.com \
--cc=gcoady@gmail.com \
--cc=hch@infradead.org \
--cc=jengelh@linux01.gwdg.de \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=zlynx@acm.org \
--cc=zwane@infradead.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