linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Steven Truelove <steven.truelove@utoronto.ca>
Cc: wli@holomorphy.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] HUGETLBFS: Align memory request to multiple of huge page size to avoid underallocating.
Date: Mon, 27 Feb 2012 15:42:17 -0800	[thread overview]
Message-ID: <20120227154217.0a0d5a06.akpm@linux-foundation.org> (raw)
In-Reply-To: <1330351768-14874-1-git-send-email-steven.truelove@utoronto.ca>

On Mon, 27 Feb 2012 09:09:28 -0500
Steven Truelove <steven.truelove@utoronto.ca> wrote:

> When calling shmget with SHM_HUGETLB, shmget aligns the request size to PAGE_SIZE, but this is not sufficient.  Modified hugetlb_file_setup to align requests to the huge page size.
> 
> Signed-off-by: Steven Truelove <steven.truelove@utoronto.ca>
> ---
>  fs/hugetlbfs/inode.c |    9 ++++++---
>  1 files changed, 6 insertions(+), 3 deletions(-)
> 
> diff --git a/fs/hugetlbfs/inode.c b/fs/hugetlbfs/inode.c
> index 1e85a7a..6c23f09 100644
> --- a/fs/hugetlbfs/inode.c
> +++ b/fs/hugetlbfs/inode.c
> @@ -938,6 +938,8 @@ struct file *hugetlb_file_setup(const char *name, size_t size,
>  	struct path path;
>  	struct dentry *root;
>  	struct qstr quick_string;
> +	struct hstate *hstate;
> +	int num_pages;
>  
>  	*user = NULL;
>  	if (!hugetlbfs_vfsmount)
> @@ -967,10 +969,11 @@ struct file *hugetlb_file_setup(const char *name, size_t size,
>  	if (!inode)
>  		goto out_dentry;
>  
> +	hstate = hstate_inode(inode);
> +	num_pages = (size + huge_page_size(hstate) - 1) >>
> +			huge_page_shift(hstate);
>  	error = -ENOMEM;
> -	if (hugetlb_reserve_pages(inode, 0,
> -			size >> huge_page_shift(hstate_inode(inode)), NULL,
> -			acctflag))
> +	if (hugetlb_reserve_pages(inode, 0, num_pages, NULL, acctflag))
>  		goto out_inode;
>  
>  	d_instantiate(path.dentry, inode);

A few things...

- sys_mmap_pgoff() does the rounding up prior to calling
  hugetlb_file_setup().  ipc/shm.c:newseg() does not.

  We should be consistent here: do it in the caller or the callee,
  not both (or neither!).  I guess doing it in the callee would be
  best.

- The above code could/should have used ALIGN().  Or round_up(): the
  difference presently escapes me, even though it was so obvious that
  we left all these things undocumented.

- What's the point in aligning the length if we don't also look at
  the start address?  If that isn't a multiple of huge_page_size(), we
  will need an additional page.

--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

       reply	other threads:[~2012-02-27 23:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1330351768-14874-1-git-send-email-steven.truelove@utoronto.ca>
2012-02-27 23:42 ` Andrew Morton [this message]
2012-02-28  2:55   ` [PATCH] HUGETLBFS: Align memory request to multiple of huge page size to avoid underallocating Steven Truelove
2012-02-28  3:04     ` Andrew Morton

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=20120227154217.0a0d5a06.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=steven.truelove@utoronto.ca \
    --cc=wli@holomorphy.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;
as well as URLs for NNTP newsgroup(s).