Date: Thu, 11 Jun 2015 16:13:53 +0200
From: Ingo Molnar <mingo@kernel.org>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Cc: Andy Lutomirski <luto@amacapital.net>,
        Andrew Morton <akpm@linux-foundation.org>,
        Denys Vlasenko <dvlasenk@redhat.com>, Brian Gerst <brgerst@gmail.com>,
        Peter Zijlstra <peterz@infradead.org>, Borislav Petkov <bp@alien8.de>,
        "H. Peter Anvin" <hpa@zytor.com>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Oleg Nesterov <oleg@redhat.com>, Thomas Gleixner <tglx@linutronix.de>,
        Waiman Long <Waiman.Long@hp.com>
Subject: Re: [RFC PATCH 00/12] x86/mm: Implement lockless
 pgd_alloc()/pgd_free()
Message-ID: <20150611141353.GA9447@gmail.com>
References: <1434031637-9091-1-git-send-email-mingo@kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1434031637-9091-1-git-send-email-mingo@kernel.org>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 815
Lines: 24


[ I fat-fingered the linux-mm Cc:, so every reply will bounce on that,
  sorry about that  :-/ Fixed it in this mail's Cc: list. ]

* Ingo Molnar <mingo@kernel.org> wrote:

> Waiman Long reported 'pgd_lock' contention on high CPU count systems and 
> proposed moving pgd_lock on a separate cacheline to eliminate false sharing and 
> to reduce some of the lock bouncing overhead.

So 'pgd_lock' is a global lock, used for every new task creation:

arch/x86/mm/fault.c:DEFINE_SPINLOCK(pgd_lock);

which with a sufficiently high CPU count starts to hurt.

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/