public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@intel.com>
To: Lukasz Odzioba <lukasz.odzioba@intel.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	akpm@linux-foundation.org, kirill.shutemov@linux.intel.com,
	mhocko@suse.com, aarcange@redhat.com, vdavydov@parallels.com,
	mingli199x@qq.com, minchan@kernel.org
Cc: lukasz.anaczkowski@intel.com
Subject: Re: [PATCH 1/1] mm/swap.c: flush lru_add pvecs on compound page arrival
Date: Wed, 8 Jun 2016 08:31:21 -0700	[thread overview]
Message-ID: <57583A49.30809@intel.com> (raw)
In-Reply-To: <1465396537-17277-1-git-send-email-lukasz.odzioba@intel.com>

On 06/08/2016 07:35 AM, Lukasz Odzioba wrote:
> diff --git a/mm/swap.c b/mm/swap.c
> index 9591614..3fe4f18 100644
> --- a/mm/swap.c
> +++ b/mm/swap.c
> @@ -391,9 +391,8 @@ static void __lru_cache_add(struct page *page)
>  	struct pagevec *pvec = &get_cpu_var(lru_add_pvec);
>  
>  	get_page(page);
> -	if (!pagevec_space(pvec))
> +	if (!pagevec_add(pvec, page) || PageCompound(page))
>  		__pagevec_lru_add(pvec);
> -	pagevec_add(pvec, page);
>  	put_cpu_var(lru_add_pvec);
>  }

Lukasz,

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?

I think if we're going to be hacking around this area, we should also
add something to vmstat or zoneinfo to spell out how many of these
things there are.

  parent reply	other threads:[~2016-06-08 15:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-08 14:35 [PATCH 1/1] mm/swap.c: flush lru_add pvecs on compound page arrival Lukasz Odzioba
2016-06-08 15:04 ` Michal Hocko
2016-06-09  8:01   ` Odzioba, Lukasz
2016-06-08 15:31 ` Dave Hansen [this message]
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

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=57583A49.30809@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