From: Peter Zijlstra <peterz@infradead.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: George Spelvin <linux@horizon.com>,
dave@sr71.net, linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux@rasmusvillemoes.dk, riel@redhat.com, rientjes@google.com,
torvalds@linux-foundation.org
Subject: Re: [PATCH 3/3 v6] mm/vmalloc: Cache the vmalloc memory info
Date: Tue, 25 Aug 2015 14:59:51 +0200 [thread overview]
Message-ID: <20150825125951.GR16853@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20150825095638.GA24750@gmail.com>
On Tue, Aug 25, 2015 at 11:56:38AM +0200, Ingo Molnar wrote:
> +void get_vmalloc_info(struct vmalloc_info *vmi)
> +{
> + unsigned int cache_gen, gen;
I see you dropped the u64 thing, good, ignore that previous email.
> +
> + /*
> + * The common case is that the cache is valid, so first
> + * read it, then check its validity.
> + *
> + * The two read barriers make sure that we read
> + * 'cache_gen', 'vmap_info_cache' and 'gen' in
> + * precisely that order:
> + */
> + cache_gen = vmap_info_cache_gen;
> + smp_rmb();
> + *vmi = vmap_info_cache;
> + smp_rmb();
> + gen = vmap_info_gen;
> +
> + /*
> + * If the generation counter of the cache matches that of
> + * the vmalloc generation counter then return the cache:
> + */
> + if (cache_gen == gen)
> + return;
There is one aspect of READ_ONCE() that is not replaced with smp_rmb(),
and that is that READ_ONCE() should avoid split loads.
Without READ_ONCE() the compiler is free to turn the loads into separate
and out of order byte loads just because its insane, thereby also making
the WRITE_ONCE() pointless.
Now I'm fairly sure it all doesn't matter much, the info can change the
moment we've copied it, so the read is inherently racy.
And by that same argument I feel this is all somewhat over engineered.
> +
> + /* Make sure 'gen' is read before the vmalloc info: */
> + smp_rmb();
> + calc_vmalloc_info(vmi);
> +
> + /*
> + * All updates to vmap_info_cache_gen go through this spinlock,
> + * so when the cache got invalidated, we'll only mark it valid
> + * again if we first fully write the new vmap_info_cache.
> + *
> + * This ensures that partial results won't be used and that the
> + * vmalloc info belonging to the freshest update is used:
> + */
> + spin_lock(&vmap_info_lock);
> + if ((int)(gen-vmap_info_cache_gen) > 0) {
> + vmap_info_cache = *vmi;
> + /*
> + * Make sure the new cached data is visible before
> + * the generation counter update:
> + */
> + smp_wmb();
> + vmap_info_cache_gen = gen;
> + }
> + spin_unlock(&vmap_info_lock);
> +}
> +
> +#endif /* CONFIG_PROC_FS */
--
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:[~2015-08-25 12:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-23 4:48 [PATCH 0/3] mm/vmalloc: Cache the /proc/meminfo vmalloc statistics George Spelvin
2015-08-23 6:04 ` Ingo Molnar
2015-08-23 6:46 ` George Spelvin
2015-08-23 8:17 ` [PATCH 3/3 v3] mm/vmalloc: Cache the vmalloc memory info Ingo Molnar
2015-08-23 20:53 ` Rasmus Villemoes
2015-08-24 6:58 ` Ingo Molnar
2015-08-24 8:39 ` Rasmus Villemoes
2015-08-23 21:56 ` Rasmus Villemoes
2015-08-24 7:00 ` Ingo Molnar
2015-08-25 16:39 ` Linus Torvalds
2015-08-25 17:03 ` Linus Torvalds
2015-08-24 1:04 ` George Spelvin
2015-08-24 7:34 ` [PATCH 3/3 v4] " Ingo Molnar
2015-08-24 7:47 ` Ingo Molnar
2015-08-24 7:50 ` [PATCH 3/3 v5] " Ingo Molnar
2015-08-24 12:54 ` George Spelvin
2015-08-25 9:56 ` [PATCH 3/3 v6] " Ingo Molnar
2015-08-25 10:36 ` George Spelvin
2015-08-25 12:59 ` Peter Zijlstra [this message]
2015-08-25 14:19 ` Rasmus Villemoes
2015-08-25 15:11 ` George Spelvin
2015-08-24 13:11 ` [PATCH 3/3 v4] " John Stoffel
2015-08-24 15:11 ` George Spelvin
2015-08-24 15:55 ` John Stoffel
2015-08-25 12:46 ` [PATCH 3/3 v3] " Peter Zijlstra
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=20150825125951.GR16853@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=dave@sr71.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@horizon.com \
--cc=linux@rasmusvillemoes.dk \
--cc=mingo@kernel.org \
--cc=riel@redhat.com \
--cc=rientjes@google.com \
--cc=torvalds@linux-foundation.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