From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933448AbdBPSHs (ORCPT ); Thu, 16 Feb 2017 13:07:48 -0500 Received: from Galois.linutronix.de ([146.0.238.70]:53489 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933006AbdBPSHc (ORCPT ); Thu, 16 Feb 2017 13:07:32 -0500 Date: Thu, 16 Feb 2017 19:07:10 +0100 (CET) From: Thomas Gleixner To: Andrew Banman cc: mingo@redhat.com, akpm@linux-foundation.org, hpa@zytor.com, mike.travis@hpe.com, rja@hpe.com, sivanich@hpe.com, x86@kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 2/6] x86/platform/uv/BAU: Add status_mmr_loc to locate message status bits In-Reply-To: <1487123931-56809-3-git-send-email-abanman@hpe.com> Message-ID: References: <1487123931-56809-1-git-send-email-abanman@hpe.com> <1487123931-56809-3-git-send-email-abanman@hpe.com> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) 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, 14 Feb 2017, Andrew Banman wrote: > The location of the ERROR and BUSY status bits depends on the descriptor > index, i.e. the CPU, of the message. We determine this location ahead of > the wait_completion loop to avoid repeating the calculation. > > Split out the status location calculation into a new routine, > status_mmr_loc, to be used within each uv*_wait_completion routine. And the reason for this is? You just tell WHAT you are doing, not the WHY. Looking at the patch which implements the uv4 wait function it uses the thing as well. So for the casual reader there is no point. The only reason i figured why you want to do that is to reduce the number of arguments to the wait function, correct? If yes, then spell it out. If no, please enlighten me. Thanks, tglx