From: "Odzioba, Lukasz" <lukasz.odzioba@intel.com>
To: "Hansen, Dave" <dave.hansen@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"kirill.shutemov@linux.intel.com"
<kirill.shutemov@linux.intel.com>,
"mhocko@suse.com" <mhocko@suse.com>,
"aarcange@redhat.com" <aarcange@redhat.com>,
"vdavydov@parallels.com" <vdavydov@parallels.com>,
"mingli199x@qq.com" <mingli199x@qq.com>,
"minchan@kernel.org" <minchan@kernel.org>
Cc: "Anaczkowski, Lukasz" <lukasz.anaczkowski@intel.com>
Subject: RE: [PATCH 1/1] mm/swap.c: flush lru_add pvecs on compound page arrival
Date: Mon, 13 Jun 2016 21:01:48 +0000 [thread overview]
Message-ID: <D6EDEBF1F91015459DB866AC4EE162CC023FA41E@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <57598E3E.3010705@intel.com>
On 09-06-16 17:42:00, Dave Hansen wrote:
> Does your workload put large pages in and out of those pvecs, though?
> If your system doesn't have any activity, then all we've shown is that
> they're not a problem when not in use. But what about when we use them?
It doesn't. To use them extensively I guess we would have to
craft a separate program for each one, which is not trivial.
> Have you, for instance, tried this on a system with memory pressure?
Not then, but here are exemplary snapshots with system using swap to handle
allocation requests with patch applied: (notation: pages = sum in bytes):
LRU_add 336 = 1344kB
LRU_rotate 158 = 632kB
LRU_deactivate 0 = 0kB
LRU_deact_file 0 = 0kB
LRU_activate 1 = 4kB
---
LRU_add 3262 = 13048kB
LRU_rotate 142 = 568kB
LRU_deactivate 0 = 0kB
LRU_deact_file 0 = 0kB
LRU_activate 6 = 24kB
---
LRU_add 3689 = 14756kB
LRU_rotate 81 = 324kB
LRU_deactivate 0 = 0kB
LRU_deact_file 0 = 0kB
LRU_activate 19 = 76kB
While running idle os we have:
LRU_add 1038 = 4152kB
LRU_rotate 0 = 0kB
LRU_deactivate 0 = 0kB
LRU_deact_file 0 = 0kB
LRU_activate 0 = 0kB
I know those are not representative in overall.
Thanks,
Lukas
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2016-06-13 21:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 14:35 Lukasz Odzioba
2016-06-08 15:04 ` Michal Hocko
2016-06-09 8:01 ` Odzioba, Lukasz
2016-06-08 15:31 ` Dave Hansen
2016-06-08 16:06 ` Michal Hocko
2016-06-08 16:34 ` Dave Hansen
2016-06-09 12:21 ` Michal Hocko
2016-06-16 18:08 ` Odzioba, Lukasz
2016-06-16 18:19 ` Michal Hocko
2016-06-16 20:03 ` Odzioba, Lukasz
2016-06-09 8:50 ` Odzioba, Lukasz
2016-06-09 15:41 ` Dave Hansen
2016-06-13 21:01 ` Odzioba, Lukasz [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=D6EDEBF1F91015459DB866AC4EE162CC023FA41E@IRSMSX103.ger.corp.intel.com \
--to=lukasz.odzioba@intel.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lukasz.anaczkowski@intel.com \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--cc=mingli199x@qq.com \
--cc=vdavydov@parallels.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