From: Michal Hocko <mhocko@suse.cz>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Hugh Dickins <hughd@google.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [patch] mm: memcontrol: use page lists for uncharge batching
Date: Mon, 21 Jul 2014 14:47:00 +0200 [thread overview]
Message-ID: <20140721124700.GD8393@dhcp22.suse.cz> (raw)
In-Reply-To: <20140718150719.GH29639@cmpxchg.org>
On Fri 18-07-14 11:07:19, Johannes Weiner wrote:
> On Thu, Jul 17, 2014 at 05:29:36PM +0200, Michal Hocko wrote:
> > On Mon 07-07-14 14:55:58, Johannes Weiner wrote:
> > > Pages are now uncharged at release time, and all sources of batched
> > > uncharges operate on lists of pages. Directly use those lists, and
> > > get rid of the per-task batching state.
> > >
> > > This also batches statistics accounting, in addition to the res
> > > counter charges, to reduce IRQ-disabling and re-enabling.
> >
> > It is probably worth noticing that there is a higher chance of missing
> > threshold events now when we can accumulate huge number of uncharges
> > during munmaps. I do not think this is earth shattering and the overall
> > improvement is worth it but changelog should mention it.
>
> Does this actually matter, though? We might deliver events a few
> pages later than before, but as I read the threshold code, once
> invoked it catches up from the last delivered threshold to the new
> usage. So we shouldn't *miss* any events.
You are right. I have completely miss this aspect of threshold
implementation. I should have looked into the code before claiming that
:/ and not focus only on the triggering code. Sorry about that!
> > > Signed-off-by: Johannes Weiner <hannes@cmpxchg.org>
> >
> > With the follow up fix from
> > http://marc.info/?l=linux-mm&m=140552814228135&w=2
> >
> > Acked-by: Michal Hocko <mhocko@suse.cz>
>
> Thanks!
>
> > > +static void uncharge_list(struct list_head *page_list)
> > > +{
> > > + struct mem_cgroup *memcg = NULL;
> > > + unsigned long nr_memsw = 0;
> > > + unsigned long nr_anon = 0;
> > > + unsigned long nr_file = 0;
> > > + unsigned long nr_huge = 0;
> > > + unsigned long pgpgout = 0;
> > > + unsigned long nr_mem = 0;
> > > + struct list_head *next;
> > > + struct page *page;
> > > +
> > > + next = page_list->next;
> > > + do {
> >
> > I would use list_for_each_entry here which would also save list_empty
> > check in mem_cgroup_uncharge_list
>
> list_for_each_entry() wouldn't work for the singleton list where we
> pass in page->lru. That's why it's a do-while that always does the
> first page before checking whether it looped back to the list head.
>
> Do we need a comment for that? I'm not convinced, there are only two
> callsites, and the one that passes the singleton page->lru is right
> below this function.
--
Michal Hocko
SUSE Labs
--
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:[~2014-07-21 12:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-07 18:55 Johannes Weiner
2014-07-17 15:29 ` Michal Hocko
2014-07-18 15:07 ` Johannes Weiner
2014-07-21 12:47 ` Michal Hocko [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=20140721124700.GD8393@dhcp22.suse.cz \
--to=mhocko@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--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