From: Adam Litke <agl@us.ibm.com>
To: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] remove hugetlb_instantiation_mutex
Date: Fri, 27 Jul 2007 11:37:57 -0500 [thread overview]
Message-ID: <1185554277.23817.18.camel@localhost.localdomain> (raw)
In-Reply-To: <1185523069.4688.115.camel@ymzhang>
Hey... I am amazed at how quickly you came back with a patch for this :)
Thanks for looking at it. Unfortunately there is one show-stopper and I
have some reservations (pun definitely intended) with your approach:
First, your patch does not pass the libhugetlbfs test
'alloc-instantiate-race' which was written to tickle the the race which
the mutex was introduced to solve. Your patch works for shared
mappings, but not for the private case.
Second, the introduction of another pair of global counters triggers my
internal warning system... These global counters are known to cause
problems with NUMA and cpusets. Have you considered these interactions?
Additionally, the commit/rollback logic you are using closely parallels
what we already do with the huge page reservation mechanism. Is there
any way you could integrate your stuff into the reservation system to
avoid all the duplicated logic?
--
Adam Litke - (agl at us.ibm.com)
IBM Linux Technology Center
next prev parent reply other threads:[~2007-07-27 16:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 7:57 [PATCH] remove hugetlb_instantiation_mutex Zhang, Yanmin
2007-07-27 16:37 ` Adam Litke [this message]
2007-07-30 7:15 ` Zhang, Yanmin
2007-08-03 16:39 ` Adam Litke
2007-08-03 16:53 ` Nish Aravamudan
2007-08-06 2:51 ` Zhang, Yanmin
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=1185554277.23817.18.camel@localhost.localdomain \
--to=agl@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yanmin_zhang@linux.intel.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