From: Gioh Kim <gioh.kim@lge.com>
To: "Andrew Morton" <akpm@linux-foundation.org>,
'김준수' <iamjoonsoo.kim@lge.com>,
"Laura Abbott" <lauraa@codeaurora.org>,
"Minchan Kim" <minchan@kernel.org>
Cc: "Michal Nazarewicz" <mina86@mina86.com>,
"Marek Szyprowski" <m.szyprowski@samsung.com>,
"Alexander Viro" <viro@zeniv.linux.org.uk>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Mel Gorman" <mel@csn.ul.ie>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
이건호 <gunho.lee@lge.com>, "'Chanho Min'" <chanho.min@lge.com>
Subject: [PATCH] CMA/HOTPLUG: clear buffer-head lru before page migration
Date: Fri, 18 Jul 2014 15:45:36 +0900 [thread overview]
Message-ID: <53C8C290.90503@lge.com> (raw)
Hi,
For page migration of CMA, buffer-heads of lru should be dropped.
Please refer to https://lkml.org/lkml/2014/7/4/101 for the history.
I have two solution to drop bhs.
One is invalidating entire lru.
Another is searching the lru and dropping only one bh that Laura proposed
at https://lkml.org/lkml/2012/8/31/313.
I'm not sure which has better performance.
So I did performance test on my cortex-a7 platform with Lmbench
that has "File & VM system latencies" test.
I am attaching the results.
The first line is of invalidating entire lru and the second is dropping selected bh.
File & VM system latencies in microseconds - smaller is better
-------------------------------------------------------------------------------
Host OS 0K File 10K File Mmap Prot Page 100fd
Create Delete Create Delete Latency Fault Fault selct
--------- ------------- ------ ------ ------ ------ ------- ----- ------- -----
10.178.33 Linux 3.10.19 25.1 19.6 32.6 19.7 5098.0 0.666 3.45880 6.506
10.178.33 Linux 3.10.19 24.9 19.5 32.3 19.4 5059.0 0.563 3.46380 6.521
I tried several times but the result tells that they are the same under 1% gap
except Protection Fault.
But the latency of Protection Fault is very small and I think it has little effect.
Therefore we can choose anything but I choose invalidating entire lru.
The try_to_free_buffers() which is calling drop_buffers() is called by many filesystem code.
So I think inserting codes in drop_buffers() can affect the system.
And also we cannot distinguish migration type in drop_buffers().
In alloc_contig_range() we can distinguish migration type and invalidate lru if it needs.
I think alloc_contig_range() is proper to deal with bh like following patch.
Laura, can I have you name on Acked-by line?
Please let me represent my thanks.
Thanks for any feedback.
------------------------------- 8< ----------------------------------
next reply other threads:[~2014-07-18 6:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 6:45 Gioh Kim [this message]
2014-07-18 7:50 ` Marek Szyprowski
2014-07-18 8:23 ` Gioh Kim
2014-07-18 9:30 ` Zhang Yanfei
2014-07-19 13:51 ` Michal Nazarewicz
2014-07-18 17:54 ` Laura Abbott
2014-07-21 2:50 ` Minchan Kim
2014-07-21 6:16 ` Gioh Kim
2014-07-21 7:36 ` Minchan Kim
2014-07-21 8:00 ` Minchan Kim
2014-07-21 13:01 ` Mel Gorman
2014-07-22 0:15 ` Minchan Kim
2014-07-22 1:04 ` Gioh Kim
2014-07-30 8:12 ` Gioh Kim
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=53C8C290.90503@lge.com \
--to=gioh.kim@lge.com \
--cc=akpm@linux-foundation.org \
--cc=chanho.min@lge.com \
--cc=gunho.lee@lge.com \
--cc=hannes@cmpxchg.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=lauraa@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.com \
--cc=mel@csn.ul.ie \
--cc=mina86@mina86.com \
--cc=minchan@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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