linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dave Hansen <dave@linux.vnet.ibm.com>
To: ebmunson@us.ibm.com
Cc: linux-mm@kvack.org, nacc <nacc@linux.vnet.ibm.com>,
	mel@csn.ul.ie, andyw <andyw@linux.vnet.ibm.com>
Subject: Re: [RFC][PATCH 2/2] Add huge page backed stack support
Date: Fri, 02 May 2008 10:11:26 -0700	[thread overview]
Message-ID: <1209748286.7763.34.camel@nimitz.home.sr71.net> (raw)
In-Reply-To: <1209693109.8483.23.camel@grover.beaverton.ibm.com>

On Thu, 2008-05-01 at 18:51 -0700, Eric B Munson wrote:
> 
> +       if (!(get_personality & HUGE_PAGE_STACK)) {
>  #ifdef CONFIG_STACK_GROWSUP
> -       stack_base = vma->vm_end + EXTRA_STACK_VM_PAGES * PAGE_SIZE;
> +               stack_base = vma->vm_end + EXTRA_STACK_VM_PAGES * PAGE_SIZE;
>  #else
> -       stack_base = vma->vm_start - EXTRA_STACK_VM_PAGES * PAGE_SIZE;
> +               stack_base = vma->vm_start - EXTRA_STACK_VM_PAGES * PAGE_SIZE;
>  #endif
> -       ret = expand_stack(vma, stack_base);
> -       if (ret)
> -               ret = -EFAULT;
> +
> +               ret = expand_stack(vma, stack_base);
> +               if (ret)
> +                       ret = -EFAULT;
> +       }

Why don't huge page stacks need to be expanded like this?  With a large
EXTRA_STACK_VM_PAGES, you would surely need this, right?

-- Dave

--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2008-05-02 17:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-02  1:51 Eric B Munson
2008-05-02 17:11 ` Dave Hansen [this message]
2008-05-02 17:20   ` Dave Hansen
2008-05-02 21:52     ` Eric B Munson
2008-05-02 17:15 ` Dave Hansen
2008-05-02 21:44   ` Eric B Munson

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=1209748286.7763.34.camel@nimitz.home.sr71.net \
    --to=dave@linux.vnet.ibm.com \
    --cc=andyw@linux.vnet.ibm.com \
    --cc=ebmunson@us.ibm.com \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    --cc=nacc@linux.vnet.ibm.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