From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from galois.linutronix.de (Galois.linutronix.de [193.142.43.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id CE32028EA for ; Thu, 20 Feb 2025 14:32:07 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=193.142.43.55 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1740061929; cv=none; b=Tb6tXNIs/1x/Ey1tPTLeDpZHXOf8pqfa0IG7okvl/gTlD4G1Cg2xhuwmtYRQotxIhMWRJ3UvqkoZPW3ySZSrLDtScopdrsj3bavX5yu85qkh45eZ8JkK3Cikod7t5O0ANpxisyX0kNnqEZz0UH85FaWml1ijkYjyNHXCDtZftIw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1740061929; c=relaxed/simple; bh=CzV9bxd149p9CWYR37KvE/72WikwSMD+HRF/P+rIC1g=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=Tfa93B74z5rtbDFFJCosCYwBGNCbrpJquEQkNyev+T/GroizzL6IjVf/qA5s6Wi89KEH4mbVgGNV0CQEEqAV+AAeoyJrH35528O2O2Nx1W4Ci3wlCCEoEx9W18oThuj3s0EPd6yagW/744rP08+h7Q3UU2g2HR0ePrV4Pw1B+9Q= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linutronix.de; spf=pass smtp.mailfrom=linutronix.de; dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=YmJ1XQLT; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=0/1TACzH; arc=none smtp.client-ip=193.142.43.55 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linutronix.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linutronix.de Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="YmJ1XQLT"; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="0/1TACzH" From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1740061926; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=1Egw6G4ZiL9DKYfKWl69qMwUYm0iJLmehOs6BqDDJDU=; b=YmJ1XQLTsqaym8YoHOcJpFK11R7Z5IKFYJHB8wl4I+VwIoQkavmxAO6IZlYKZ0IPY6sJHe Qm034pTEawWB2Ua/u22sF0kxQX7KrokFxjT2+np/SBUqw46P+HuwszktbPNaaAhAeEcvQQ PmxqqVwM2CzBhzDKik9zq/hc5qtunR4FuoiYL5yOkeXTi1wY/Qz5pvg+sWg8qTppoEZRpr MncL4jym29W24mHlmBYbsFVK7gwn5TPO+PgwhGRLWgA0L1ip2+tNJPg3DgysSIRMZwAlsU MnDZMap5XXsa3Wn3Id4sQU+bHqIkKWWD+ohNp2hx+wMziunXudKfbOITR26HWg== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1740061926; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=1Egw6G4ZiL9DKYfKWl69qMwUYm0iJLmehOs6BqDDJDU=; b=0/1TACzHVdWsCK/pbUNKLkLkppM0yhrm8leecBpvcyK4jKkj88p1OQiMVLBRhA0Ir3PLd4 fqlEXVM8aFAaltAA== To: Eric Dumazet Cc: Anna-Maria Behnsen , Frederic Weisbecker , linux-kernel , Benjamin Segall , Eric Dumazet Subject: Re: [PATCH V2 1/4] posix-timers: Make next_posix_timer_id an atomic_t In-Reply-To: <87h64oiuey.ffs@tglx> References: <20250219125522.2535263-1-edumazet@google.com> <20250219125522.2535263-2-edumazet@google.com> <87wmdlhwa8.ffs@tglx> <87h64oiuey.ffs@tglx> Date: Thu, 20 Feb 2025 15:32:05 +0100 Message-ID: <8734g8it5m.ffs@tglx> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On Thu, Feb 20 2025 at 15:04, Thomas Gleixner wrote: > On Thu, Feb 20 2025 at 09:49, Eric Dumazet wrote: >> On Thu, Feb 20, 2025 at 9:09=E2=80=AFAM Thomas Gleixner wrote: >>> > This allows the following patch to use RCU. >>> >>> Your patch ordering is slightly off by two :) >>> >>> And it fails to explain for what RCU can be used.... >> >> This is explained in the following patches. > > The changelog of a patch has to be self contained. The 'following patch' > has no meaning when the patch is merged. That said, please just fold this into the patch which actually does this RCU lookup upfront. The change is trivial enough that it does not really require to be seperate. If the lockless increment would cause issues, then the subsequent RCU lookup is the least of the worries :) Thanks, tglx