From: William Lee Irwin III <wli@holomorphy.com>
To: Rohit Seth <rseth@unix-os.sc.intel.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, akpm@digeo.com,
torvalds@transmeta.com, rohit.seth@intel.com
Subject: Re: hugetlb page patch for 2.5.48-bug fixes
Date: Thu, 21 Nov 2002 15:51:27 -0800 [thread overview]
Message-ID: <20021121235127.GS23425@holomorphy.com> (raw)
In-Reply-To: <3DDD58C1.9020503@unix-os.sc.intel.com>
On Thu, Nov 21, 2002 at 02:05:53PM -0800, Rohit Seth wrote:
> Linus, Andrew,
> Attached is the hugetlbpage patch for 2.5.48 containing following main
> changes:
> 1) Bug fixes (mainly in the unsuccessful attempts of hugepages).
> 2) Removal of Radix Tree field in key structure (as it is not needed).
> 3) Include the IPC_LOCK for permission to use hugepages.
> 4) Increment the key_counts during forks.
Okay, first off why are you using a list linked through page->private?
page->list is fully available for such tasks.
Second, the if (key == NULL) check in hugetlb_release_key() is bogus;
someone is forgetting to check for NULL, probably in
alloc_shared_hugetlb_pages().
Third, the hugetlb_release_key() in unmap_hugepage_range() is the one
that should be removed [along with its corresponding mark_key_busy()],
not the one in sys_free_hugepages(). unmap_hugepage_range() is doing
neither setup nor teardown of the key itself, only the pages and PTE's.
I would say key-level refcounting belongs to sys_free_hugepages().
Bill
WARNING: multiple messages have this Message-ID (diff)
From: William Lee Irwin III <wli@holomorphy.com>
To: Rohit Seth <rseth@unix-os.sc.intel.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, akpm@digeo.com,
torvalds@transmeta.com, rohit.seth@intel.com
Subject: Re: hugetlb page patch for 2.5.48-bug fixes
Date: Thu, 21 Nov 2002 15:51:27 -0800 [thread overview]
Message-ID: <20021121235127.GS23425@holomorphy.com> (raw)
In-Reply-To: <3DDD58C1.9020503@unix-os.sc.intel.com>
On Thu, Nov 21, 2002 at 02:05:53PM -0800, Rohit Seth wrote:
> Linus, Andrew,
> Attached is the hugetlbpage patch for 2.5.48 containing following main
> changes:
> 1) Bug fixes (mainly in the unsuccessful attempts of hugepages).
> 2) Removal of Radix Tree field in key structure (as it is not needed).
> 3) Include the IPC_LOCK for permission to use hugepages.
> 4) Increment the key_counts during forks.
Okay, first off why are you using a list linked through page->private?
page->list is fully available for such tasks.
Second, the if (key == NULL) check in hugetlb_release_key() is bogus;
someone is forgetting to check for NULL, probably in
alloc_shared_hugetlb_pages().
Third, the hugetlb_release_key() in unmap_hugepage_range() is the one
that should be removed [along with its corresponding mark_key_busy()],
not the one in sys_free_hugepages(). unmap_hugepage_range() is doing
neither setup nor teardown of the key itself, only the pages and PTE's.
I would say key-level refcounting belongs to sys_free_hugepages().
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-11-21 23:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-21 22:05 hugetlb page patch for 2.5.48-bug fixes Rohit Seth
2002-11-21 23:51 ` William Lee Irwin III [this message]
2002-11-21 23:51 ` William Lee Irwin III
-- strict thread matches above, loose matches on Subject: below --
2002-11-22 1:54 Seth, Rohit
2002-11-22 1:54 ` Seth, Rohit
2002-11-22 2:04 ` William Lee Irwin III
2002-11-22 2:04 ` William Lee Irwin III
2002-11-22 3:23 Seth, Rohit
2002-11-22 3:23 ` Seth, Rohit
2002-11-24 14:44 ` Ed Tomlinson
2002-11-24 14:44 ` Ed Tomlinson
2002-11-24 14:49 ` William Lee Irwin III
2002-11-24 14:49 ` William Lee Irwin III
2002-11-24 15:01 ` Ed Tomlinson
2002-11-24 15:01 ` Ed Tomlinson
2002-11-24 15:00 ` William Lee Irwin III
2002-11-24 15:00 ` William Lee Irwin III
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=20021121235127.GS23425@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rohit.seth@intel.com \
--cc=rseth@unix-os.sc.intel.com \
--cc=torvalds@transmeta.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.