From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 834795680 for ; Mon, 5 May 2025 19:00:52 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1746471652; cv=none; b=GA/wh5k7qnFKs1G04KpLnOqML6yXC9YAcl8akdSBGYcJcfNhHMX3/qJwBzbVbjxcoyfUYJe+OmXgtYSE5Mdl7XMiW7ji8h4H4ma7KivihISkofmRVWjPJaXORi4d8/e+56QJdTElwSHH9a/8nzQOZrikVYI/1GWoGDGD8Om0ZRE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1746471652; c=relaxed/simple; bh=0vspP+B5ayYWMsJ0nfosh2YZpUYZs4yfHDyqPwHT3iE=; h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=YrEGD0bABZdWyXjceyMSHueMK9UJKVqEHfCStb1gydQSa7vbJ02xNSB7m3QzEAhoNdcUZnUHIxMkR491VxyPuzIkCBO6ideT8ujuheq8jBkESBraCNn3EMDFnBkqV5yjtVYA8CEjTrGZwUT5K3hCxsJS/3BFjVaDbQ55GDmX3EU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=RHpjbDNx; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="RHpjbDNx" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 92B14C4CEF3; Mon, 5 May 2025 19:00:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1746471651; bh=0vspP+B5ayYWMsJ0nfosh2YZpUYZs4yfHDyqPwHT3iE=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=RHpjbDNxs8nlr0ScjHDGtdCPq8RjEAaPFjjFLqaoIqQCEF75C/6zJP5BlxZ+m/YOr bv0izmtOMt6VxggbOP42++Hfu4TFatNBDAgYgtCuotfaP9omTyPns/u2xNMRrWqD6L FLyqWIzj5YZzbV7Ubvf/VdTpVoI4TemjCQHaeVLLic8ioAc80Hoy8kHcP6mpy4FeQ1 eQGDFibPmnWU5y6FvXoqtB9LZdXzrlxNwGQrjEJDEcGVT2dil5gMMGjrdLjo4aQsZh qR/ZFOKxuMwjdTqMuVu4pfiWjnSoaWUf4G2/0dPwl1bC9mmcxR4qXAFdSRa9L5Hkge EJyH/ijXSzSBg== Date: Mon, 5 May 2025 12:00:50 -0700 From: Jakub Kicinski To: "Olech, Milena" Cc: "Nguyen, Anthony L" , "davem@davemloft.net" , "pabeni@redhat.com" , "edumazet@google.com" , "andrew+netdev@lunn.ch" , "netdev@vger.kernel.org" , "Kitszel, Przemyslaw" , "Keller, Jacob E" , "richardcochran@gmail.com" , "Hay, Joshua A" , "Salin, Samuel" Subject: Re: [PATCH net-next v2 10/11] idpf: add Tx timestamp flows Message-ID: <20250505120050.129d10ee@kernel.org> In-Reply-To: References: <20250425215227.3170837-1-anthony.l.nguyen@intel.com> <20250425215227.3170837-11-anthony.l.nguyen@intel.com> <20250428173521.1af2cc52@kernel.org> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Mon, 5 May 2025 17:08:12 +0000 Olech, Milena wrote: > I see your point, and I've had a long discussion with Olek Lobakin - > we tried to prevent all possible deadlocks, and the conclusion was > that adding lock_bh in BH may be considered as overhead. =46rom my comment it seems that I saw a caller from a work, not from BH. > BUT maybe I'm missing something - do you see any scenario where > the flow may break?