From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754354Ab0LGPHk (ORCPT ); Tue, 7 Dec 2010 10:07:40 -0500 Received: from smtp110.prem.mail.ac4.yahoo.com ([76.13.13.93]:44108 "HELO smtp110.prem.mail.ac4.yahoo.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1753073Ab0LGPHi (ORCPT ); Tue, 7 Dec 2010 10:07:38 -0500 X-Yahoo-SMTP: _Dag8S.swBC1p4FJKLCXbs8NQzyse1SYSgnAbY0- X-YMail-OSG: .hKCbBEVM1l0wsrunwoAwJaBqacVN7V8monejTxRmgoGdBO 0nwyxBeloTUjCDJ6NXTup43zvTxhfCwhlCUkSpvDnjZI3y_9..KvjOnl8_wi BmPFWrFv_RhH2.KXAHo1_bGdHFYV3CSM_elXpDcVD.Hkvsvx9ecthEXZlXK5 s4cWU0uw3gnujIpw2jbYBDma6QbFWw.rc8z.LKFDjr7zTJGeLnESC7w1x..8 Dj5lzYnuv31TTMeIBE6v3F2R5ecrYEzX5b49yPNQ- X-Yahoo-Newman-Property: ymail-3 Date: Tue, 7 Dec 2010 09:07:35 -0600 (CST) From: Christoph Lameter X-X-Sender: cl@router.home To: Tejun Heo cc: akpm@linux-foundation.org, Yinghai Lu , Ingo Molnar , Pekka Enberg , linux-kernel@vger.kernel.org, Eric Dumazet , Mathieu Desnoyers Subject: Re: [Use cpuops V1 04/11] x86: Use this_cpu_ops for current_cpu_data accesses In-Reply-To: <4CFE4BE0.9040203@kernel.org> Message-ID: References: <20101206171618.302060721@linux.com> <20101206171638.595205962@linux.com> <4CFE41F8.7040400@kernel.org> <4CFE4294.30001@kernel.org> <4CFE4BE0.9040203@kernel.org> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 7 Dec 2010, Tejun Heo wrote: > >> Ooh, was too fast. I think mixing the use of percpu accesses to > >> cpu_info and the wrapper macro current_cpu_data is quite confusing. > >> There aren't too many current_cpu_data users in x86 anyway. Can you > >> please make the conversion complete? I'm moving the above misplaced > >> chunk into 03 and not applying 04 for now. > > > > We cannot make that conversion complete since we cannot obtain the address > > if we use a this_cpu operation. Then its better to drop this patch. > > No, I was talking about dropping current_cpu_data macro. We can use > __this_cpu_ptr() for addresses. I just find it very confusing to mix > current_cpu_data and using direct percpu accessors on cpu_info. Hmmm... Ok 21 occurrences. So two patches: Conversion and then this_cpu_ops. Or one doing both?