From: Stefan Roscher <ossrosch-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org
Cc: Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>,
Alexander Schmidt
<alexs-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>,
Linux RDMA <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Joachim Fenkes <fenkes-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>,
Alex Vainman
<alexonlists-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Christoph Raisch <raisch-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>,
Hoang-Nam Nguyen
<hnguyen-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>,
Stefan Roscher
<stefan.roscher-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>,
Mel Gorman <MELGOR-g5DgMFWsQ8jQT0dZR+AlfA@public.gmane.org>
Subject: Re: [ewg] [RFC] libibverbs: ibv_fork_init() and libhugetlbfs
Date: Tue, 18 May 2010 13:04:05 +0200 [thread overview]
Message-ID: <201005181304.05592.ossrosch@linux.vnet.ibm.com> (raw)
In-Reply-To: <adafx1xul8v.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
Hi Roland,
On Wednesday 12 May 2010 06:40:16 pm Roland Dreier wrote:
> > * added get_huge_page_size() to read the huge page size from
> > /proc/meminfo. This is done at ibv_fork_init() time.
>
> That doesn't work on systems that have multiple huge page sizes (eg
> powerpc). You can compare the code to get the size in libhugetlbfs.
>
> Also I think the munging through /proc/pid/maps doesn't really work.
> First of all, essentially grepping for libhugetlbfs is not robust as I
> mentioned -- this will break in the same way for apps using huge pages
> directly.
I agree that this two points (multiple huge page sizes and performance) are two critical
issues which we have to attack.
One suggestion from our side would be to use /proc/pid/smaps which would workaround
the multiple huge page size problem. It would not solve the perfomance issue, because
reading the file would assume long time even if we buffer the ranges and pagesize during
fork_init.
Do you have an oppinion on that?
We appreciate your help!
regards Stefan
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-05-18 11:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 7:39 [RFC] libibverbs: ibv_fork_init() and libhugetlbfs Alexander Schmidt
2010-05-06 20:55 ` Roland Dreier
[not found] ` <adavdb092d8.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
2010-05-07 10:19 ` Alexander Schmidt
2010-05-12 16:40 ` Roland Dreier
[not found] ` <adafx1xul8v.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
2010-05-18 11:04 ` Stefan Roscher [this message]
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=201005181304.05592.ossrosch@linux.vnet.ibm.com \
--to=ossrosch-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
--cc=MELGOR-g5DgMFWsQ8jQT0dZR+AlfA@public.gmane.org \
--cc=alexonlists-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=alexs-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
--cc=ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org \
--cc=fenkes-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org \
--cc=hnguyen-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=raisch-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org \
--cc=rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org \
--cc=stefan.roscher-tA70FqPdS9bQT0dZR+AlfA@public.gmane.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