From: Dave Hansen <dave.hansen@intel.com>
To: "Odzioba, Lukasz" <lukasz.odzioba@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: Thu, 9 Jun 2016 08:41:50 -0700 [thread overview]
Message-ID: <57598E3E.3010705@intel.com> (raw)
In-Reply-To: <D6EDEBF1F91015459DB866AC4EE162CC023F8EBE@IRSMSX103.ger.corp.intel.com>
On 06/09/2016 01:50 AM, Odzioba, Lukasz wrote:
> On 08-06-16 17:31:00, Dave Hansen wrote:
>> Do we have any statistics that tell us how many pages are sitting the
>> lru pvecs? Although this helps the problem overall, don't we still have
>> a problem with memory being held in such an opaque place?
>
>>From what I observed the problem is mainly with lru_add_pvec, the
> rest is near empty for most of the time. I added debug code to
> lru_add_drain_all(), to see sizes of the lru pvecs when I debugged this.
>
> Among lru_add_pvec, lru_rotate_pvecs, lru_deactivate_file_pvecs,
> lru_deactivate_pvecs, activate_page_pvecs almost all (3-4GB) of the
> missing memory was in lru_add_pvec, the rest was almost always empty.
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?
Have you, for instance, tried this on a system with memory pressure?
--
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>
next prev parent reply other threads:[~2016-06-09 15:41 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 [this message]
2016-06-13 21:01 ` Odzioba, Lukasz
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=57598E3E.3010705@intel.com \
--to=dave.hansen@intel.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lukasz.anaczkowski@intel.com \
--cc=lukasz.odzioba@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