From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934885AbcCOR2K (ORCPT ); Tue, 15 Mar 2016 13:28:10 -0400 Received: from mail-wm0-f53.google.com ([74.125.82.53]:35794 "EHLO mail-wm0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934777AbcCOR2I (ORCPT ); Tue, 15 Mar 2016 13:28:08 -0400 Date: Tue, 15 Mar 2016 18:28:04 +0100 From: Frederic Weisbecker To: Linus Torvalds Cc: Ingo Molnar , Linux Kernel Mailing List , Thomas Gleixner , Peter Zijlstra , Andrew Morton Subject: Re: [PATCH] nohz: Change tick_dep_mask from 'unsigned long' to 'unsigned int' Message-ID: <20160315172803.GB5058@lerouge> References: <20160314123200.GA15971@gmail.com> <20160315095337.GC7943@gmail.com> <20160315121525.GA3991@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Mar 15, 2016 at 09:30:49AM -0700, Linus Torvalds wrote: > On Tue, Mar 15, 2016 at 5:15 AM, Ingo Molnar wrote: > > > > Hm, so the problem I did not consider is the following: > > > > triton:~/tip> git grep tick_dep_mask kernel | grep _bit > > kernel/time/tick-sched.c: clear_bit(bit, &ts->tick_dep_mask); > > kernel/time/tick-sched.c: clear_bit(bit, &tsk->tick_dep_mask); > > kernel/time/tick-sched.c: clear_bit(bit, &sig->tick_dep_mask); Ah! Now I remember why I used unsigned long :-s > > Ahh. I missed that too. > > Ok, leave the 64-bit field for now, while we think about this. But one > option is to just use "atomic_andnot()" instead of clear_bit(). > > That would imply using an "atomic_t", which would be fairly natural > (and would be 32-bit). I can try that. And then we would end up with atomic_fetch_or() and maybe the scheduler could keep its ad-hoc version until thread_info types get unified (if that's possible). > > And wouldn't it be so nice if "thread_info->flags" would just be > atomic_t too. Right now we use a mixture of bit-ops and ACCESS_ONCE() > (and many codepaths then doing neither, and just accessing it > directly, ignoring any races. > > Oh well. I can try that too while at it :-)