From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755251AbaEFUaT (ORCPT ); Tue, 6 May 2014 16:30:19 -0400 Received: from bombadil.infradead.org ([198.137.202.9]:51461 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751775AbaEFUaN (ORCPT ); Tue, 6 May 2014 16:30:13 -0400 Date: Tue, 6 May 2014 22:30:06 +0200 From: Peter Zijlstra To: Mel Gorman Cc: Linux-MM , Linux-FSDevel , Johannes Weiner , Vlastimil Babka , Jan Kara , Michal Hocko , Hugh Dickins , Linux Kernel Subject: Re: [PATCH 17/17] mm: filemap: Avoid unnecessary barries and waitqueue lookup in unlock_page fastpath Message-ID: <20140506203006.GF1429@laptop.programming.kicks-ass.net> References: <1398933888-4940-1-git-send-email-mgorman@suse.de> <1398933888-4940-18-git-send-email-mgorman@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1398933888-4940-18-git-send-email-mgorman@suse.de> User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 01, 2014 at 09:44:48AM +0100, Mel Gorman wrote: > +/* > + * If PageWaiters was found to be set at unlock time, __wake_page_waiters > + * should be called to actually perform the wakeup of waiters. > + */ > +static inline void __wake_page_waiters(struct page *page) > +{ > + ClearPageWaiters(page); -ENOCOMMENT barriers should always come with a comment that explain the memory ordering and reference the pairing barrier. Also, FWIW, there's a mass rename queued for .16 that'll make this: smp_mb__after_atomic(); but for now it will also still provide the old names with a __deprecated tag on, so no real harm. > + smp_mb__after_clear_bit(); > + wake_up_page(page, PG_locked); > +}