From: "Radosław Smogura" <mail@smogura.eu>
To: linux-mm@kvack.org
Subject: Hugepages for shm page cache (defrag)
Date: Wed, 6 Jul 2011 21:31:01 +0200 [thread overview]
Message-ID: <201107062131.01717.mail@smogura.eu> (raw)
[-- Attachment #1: Type: Text/Plain, Size: 1124 bytes --]
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.
-------------------
Idea is that I created defrag method which tries to defragment page cache to
huge page, I added one flag for such compound page, as I want to treat it
little different, for example any put/get unless/test zero will increase it
count, so page will be freed if all "sub-pages" will be freed. From other side
each tail page may have it's own LRU (why I don't know).
There is ofocourse much work to do in shm to make it hugepage aware, map
pte(pde) etc.
At this stage I don't have BUGs and I can make 2MB shm area, read and delete
it.
Signed-off-by: Radosław Smogura (mail@smogura.eu)
-------------------
Any suggestion are welcome.
If it's to early work I want to say sorry. I hope I fullfiled all code/submit
conventions.
Regards,
Radosław Smogura
[-- Attachment #2: defrag_page_cache_01.patch.gz --]
[-- Type: application/x-gzip, Size: 5064 bytes --]
next reply other threads:[~2011-07-06 19:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 19:31 Radosław Smogura [this message]
2011-07-07 5:28 ` Hugepages for shm page cache (defrag) Andi Kleen
2011-07-07 12:02 ` mail
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=201107062131.01717.mail@smogura.eu \
--to=mail@smogura.eu \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).