From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id F3863C83F12 for ; Wed, 30 Aug 2023 01:05:38 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240631AbjH3BFI (ORCPT ); Tue, 29 Aug 2023 21:05:08 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39162 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S241546AbjH3BFG (ORCPT ); Tue, 29 Aug 2023 21:05:06 -0400 Received: from mail-io1-xd36.google.com (mail-io1-xd36.google.com [IPv6:2607:f8b0:4864:20::d36]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 302CECF3 for ; Tue, 29 Aug 2023 18:04:46 -0700 (PDT) Received: by mail-io1-xd36.google.com with SMTP id ca18e2360f4ac-79277cfc73bso184513739f.1 for ; Tue, 29 Aug 2023 18:04:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelfernandes.org; s=google; t=1693357485; x=1693962285; darn=vger.kernel.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=suY/CmSomjB8J4jX+yIP8mDM9LC2Ww7xj6ma0dhVjb4=; b=R8jqpHwx0PKTwD+TZiqTgoM+mVEvzDSgQFJ19xmdNbXqgsFaLlUnpnfQ7//x+RQXaB CZ2So7pSjbu2PlGqaRkegNguP7UCW3Ssu7jAl+3FpLTq4gstQfyNsqpHymd9C7ob65ef mRkdDqxIVw44s5PqMsL76T+UlQ35iWhfcF0IE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693357485; x=1693962285; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=suY/CmSomjB8J4jX+yIP8mDM9LC2Ww7xj6ma0dhVjb4=; b=U+MPDxz+eZZCmicMrPZaRCAp/PZt7iZchD98h1A2xB4PIOOt4z0KFeuuDjW4KWlWIA vMlxE0xaVCjHCs05h2dfH6OgqOI8eXtHv14H6t7JTYkspbplQ5a8WX5Fbgrct111XB8t 5LC9S8u3ctyDN2t9D4r9P3G7A0JFF2MiuX1V4LK7T18vtpE1h23ny1DLz5M0Tv9prxUv ildDziW8F0TmMu2X0nKNBRwUKqt9FxcD1oFhvUXfyK+PwxNIrq0lERiTKTqN73qSi6R1 9iUXGyHizxaYyIykeek/fUTYLXORYj1VnMcDExFW+ICUapsNQSyj0cA5tE1L7SFNlfbd H7xQ== X-Gm-Message-State: AOJu0YzM52FuyM2N0HT3FEWz0XXqOueteMuDhRgJYqUq/EP/+W4RezW2 AsrFCdENR7v8WwlKGT/fQdFKZtjiWbTt5EiS3fw= X-Google-Smtp-Source: AGHT+IECJsS18QECLLOZkmJFqx1c1+vSNRvmV5BUx60dgeATp6olnHx4jzT1XR8OvpyVBFzC5vRL/g== X-Received: by 2002:a6b:d902:0:b0:790:fab3:2052 with SMTP id r2-20020a6bd902000000b00790fab32052mr975418ioc.5.1693357485541; Tue, 29 Aug 2023 18:04:45 -0700 (PDT) Received: from localhost (156.190.123.34.bc.googleusercontent.com. [34.123.190.156]) by smtp.gmail.com with ESMTPSA id fn6-20020a056638640600b0042b52dc77e3sm3453217jab.158.2023.08.29.18.04.44 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 29 Aug 2023 18:04:44 -0700 (PDT) Date: Wed, 30 Aug 2023 01:04:44 +0000 From: Joel Fernandes To: Huacai Chen Cc: paulmck@kernel.org, Thomas Gleixner , Z qiang , Huacai Chen , Frederic Weisbecker , Neeraj Upadhyay , Josh Triplett , Boqun Feng , Ingo Molnar , John Stultz , Stephen Boyd , Steven Rostedt , Mathieu Desnoyers , Lai Jiangshan , Sergey Senozhatsky , rcu@vger.kernel.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org, Binbin Zhou Subject: Re: [PATCH V4 2/2] rcu: Update jiffies in rcu_cpu_stall_reset() Message-ID: <20230830010444.GA33437@google.com> References: <20230825232807.GA97898@google.com> <2681134d-cc88-49a0-a1bc-4ec0816288f6@paulmck-laptop> <20230828133348.GA1553000@google.com> <142b4bff-6a2e-4ea0-928c-3cfe9befa403@paulmck-laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Mon, Aug 28, 2023 at 11:12:49PM +0800, Huacai Chen wrote: > Maybe putting > nr_fqs_jiffies_stall before jiffies_force_qs is better, because I > think putting an 'int' between two 'long' is wasting space. :) Though it is a decent suggestion, moving it before jiffies_force_qs does not make the structure smaller. Trying to outsmart the compiler seems not a good idea when it is not really packing the structure. Besides, I am not too worried about 4-byte holes considering the structure is full of them and that ofl_lock is ____cacheline_internodealigned_in_smp which adds a giant 55 byte hole to the structure. That should keep you at night if you are worried about 4 byte holes. And the total size of the structure on a 64-bit build is 3776 bytes so 4 bytes is about 1/10th of a percent. Puny. So I'd rather leave nr_fqs_jiffies_stall where it is especially considering it is more readable where it is. :-) thanks, - Joel > > Huacai > > > > > Thanks.