From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-187.mta0.migadu.com (out-187.mta0.migadu.com [91.218.175.187]) (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 D3C711D61B1 for ; Tue, 18 Feb 2025 23:38:36 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.187 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1739921918; cv=none; b=YhzpsfQCZThes7LZf3EV78ph5O0LlACaKrdNpyBmCiLr5G3feZdvUAeuYPzecr7GanpSC+e3EmGlau37kc+0D73YfpT+6SXEA/Ilcjcvvh1b1jtlJP7utAhooDSbNbCmvjyyfpZjo8JHMl5xMIC10/R/CU+8hU1876meo3wTXSc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1739921918; c=relaxed/simple; bh=54FVSRGcC2rsBfqo3QsjOLWTLAJZC/VditjcootSkbY=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=CuTC5MokCWEBShlK0UTZiv3yjf6+Dgad1n8yzQPRWooiDVPzlm5WbU3qKdLknCy6cCSWNO97SzEFVLKpvvQZy+Bfyro6obOL1/w5qwmon2ge5SVKcsZ9MwkbQjYhHnx+Q1SmtXMMTXxK0UWlxexQlt31MVI7u1FdieZ7mcZatv8= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=tnXpOafl; arc=none smtp.client-ip=91.218.175.187 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="tnXpOafl" Message-ID: <4dc10429-29dd-47bb-bd5f-6a8654ed2fec@linux.dev> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1739921904; 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=54FVSRGcC2rsBfqo3QsjOLWTLAJZC/VditjcootSkbY=; b=tnXpOaflyyC9voJnYySLhiqkXORPjFW742YwlsbnkOM2als1VylXMMl5xLhvDj+qgk9EQ0 rb+qEdChd6aFUC6CoPyyLNK1bKV4WigoiDmWU+FkWQpAVxw9kOHi1i+Qeon5E+Coi9ox3u 8FFWh+m4QZ9rt+54/70O4cIC7Zq19io= Date: Tue, 18 Feb 2025 15:38:17 -0800 Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Subject: Re: [PATCH bpf-next v2 1/3] tcp: add TCP_RTO_MAX_MIN_SEC definition To: Jason Xing Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org, pabeni@redhat.com, dsahern@kernel.org, kuniyu@amazon.com, ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org, eddyz87@gmail.com, song@kernel.org, yonghong.song@linux.dev, john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com, jolsa@kernel.org, shuah@kernel.org, ykolal@fb.com, bpf@vger.kernel.org, netdev@vger.kernel.org References: <20250217034245.11063-1-kerneljasonxing@gmail.com> <20250217034245.11063-2-kerneljasonxing@gmail.com> Content-Language: en-US X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Martin KaFai Lau In-Reply-To: <20250217034245.11063-2-kerneljasonxing@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Migadu-Flow: FLOW_OUT On 2/16/25 7:42 PM, Jason Xing wrote: > Add minimum value definition as the lower bound of RTO MAX > set by users. No functional changes here. If it is no-op, why it is needed? The commit message didn't explain it either. I also cannot guess how patch 2 depends on patch 1. pw-bot: cr