From: mail@rsmogura.net
To: Andi Kleen <andi@firstfloor.org>
Cc: "Radosław Smogura" <mail@smogura.eu>,
linux-mm@kvack.org, aarcange@redhat.com
Subject: Re: Hugepages for shm page cache (defrag)
Date: Thu, 07 Jul 2011 08:02:44 -0400 [thread overview]
Message-ID: <5be3df4081574f3d4e1e699f028549a7@rsmogura.net> (raw)
In-Reply-To: <m2pqlmy7z8.fsf@firstfloor.org>
On Wed, 06 Jul 2011 22:28:59 -0700, Andi Kleen wrote:
> RadosA?aw Smogura <mail@smogura.eu> writes:
>
>> Hello,
>>
>> This is may first try with Linux patch, so please do not blame me
>> too much.
>> Actually I started with small idea to add MAP_HUGTLB for /dev/shm
>> but it grew
>> up in something more like support for huge pages in page cache, but
>> according
>> to documentation to submit alpha-work too, I decided to send this.
>
> Shouldn't this be rather integrated with the normal transparent huge
> pages? It seems odd to develop parallel infrastructure.
>
> -Andi
It's not quite good to ask me about this, as I'm starting hacker, but I
think it should be treated as counterpart for page cache, and actually I
got few "collisions" with THP.
High level design will probably be the same (e.g. I use defrag_, THP
uses collapse_ for creating huge page), but in contrast I try to operate
on page cache, so in some way file system must be huge page aware (shm
fs is not, as it can move page from page cache to swap cache - it may
silently fragment de-fragmented areas).
I put some requirements for work, e. g. mapping file as huge should not
affect previous or future, even fancy, non huge mappings, both callers
should succeed and get this what they asked for.
Of course I think how to make it more "transparent" without need of
file system support, but I suppose it may be dead-corner.
I still want to emphasise it's really alpha version.
Regards,
Radek
--
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>
next prev parent reply other threads:[~2011-07-07 12:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 19:31 Radosław Smogura
2011-07-07 5:28 ` Andi Kleen
2011-07-07 12:02 ` mail [this message]
2011-07-08 0:07 ` Hugh Dickins
2011-07-14 20:15 ` mail
2011-07-15 19:50 ` Hugh Dickins
2011-07-30 16:15 ` [PATCH] Changes how ref-count of compound pages are managed Radosław Smogura
2011-08-07 17:03 ` Hugepages for shm page cache (defrag) Radosław Smogura
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=5be3df4081574f3d4e1e699f028549a7@rsmogura.net \
--to=mail@rsmogura.net \
--cc=aarcange@redhat.com \
--cc=andi@firstfloor.org \
--cc=linux-mm@kvack.org \
--cc=mail@smogura.eu \
/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