Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=amazon.com header.i=@amazon.com header.b="RDahEyiw" Received: from smtp-fw-6002.amazon.com (smtp-fw-6002.amazon.com [52.95.49.90]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F0B9ED67 for ; Mon, 11 Dec 2023 07:58:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=@amazon.com; q=dns/txt; s=amazon201209; t=1702310294; x=1733846294; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=HXYwtHf1crZ+2R2c/ebu/5qXB2tr3ce7Wh+7+A6s3a4=; b=RDahEyiwofZOUkNeCmV6FVfH73NaooSFrDOznoBJnzUdp1zxRuF64xgF bjYfLTaJIHYnC+IfUO8oUHeLMeWG5ZwUZZzPb5WyMt0Q5gFGJf3RHtA21 SjyhmmRb/E5X2ZqFGc9DcBuNFdOdJgaVxLowNLkXK+ZPoOpB+zExMNOpz c=; X-IronPort-AV: E=Sophos;i="6.04,268,1695686400"; d="scan'208";a="373069424" Received: from iad12-co-svc-p1-lb1-vlan3.amazon.com (HELO email-inbound-relay-pdx-2c-m6i4x-e7094f15.us-west-2.amazon.com) ([10.43.8.6]) by smtp-border-fw-6002.iad6.amazon.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 11 Dec 2023 15:58:11 +0000 Received: from smtpout.prod.us-west-2.prod.farcaster.email.amazon.dev (pdx2-ws-svc-p26-lb5-vlan3.pdx.amazon.com [10.39.38.70]) by email-inbound-relay-pdx-2c-m6i4x-e7094f15.us-west-2.amazon.com (Postfix) with ESMTPS id 3F74240BBD; Mon, 11 Dec 2023 15:58:10 +0000 (UTC) Received: from EX19MTAUWC001.ant.amazon.com [10.0.21.151:39557] by smtpin.naws.us-west-2.prod.farcaster.email.amazon.dev [10.0.54.33:2525] with esmtp (Farcaster) id 6e28f5eb-e4d4-4630-8c60-59d7042c6070; Mon, 11 Dec 2023 15:58:09 +0000 (UTC) X-Farcaster-Flow-ID: 6e28f5eb-e4d4-4630-8c60-59d7042c6070 Received: from EX19D003UWC004.ant.amazon.com (10.13.138.150) by EX19MTAUWC001.ant.amazon.com (10.250.64.174) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.40; Mon, 11 Dec 2023 15:58:09 +0000 Received: from EX19MTAUEA001.ant.amazon.com (10.252.134.203) by EX19D003UWC004.ant.amazon.com (10.13.138.150) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.40; Mon, 11 Dec 2023 15:58:09 +0000 Received: from dev-dsk-abuehaze-1c-21d23c85.eu-west-1.amazon.com (10.13.244.41) by mail-relay.amazon.com (10.252.134.102) with Microsoft SMTP Server id 15.2.1118.40 via Frontend Transport; Mon, 11 Dec 2023 15:58:09 +0000 Received: by dev-dsk-abuehaze-1c-21d23c85.eu-west-1.amazon.com (Postfix, from userid 5005603) id D84D9172A; Mon, 11 Dec 2023 15:58:08 +0000 (UTC) From: Hazem Mohamed Abuelfotoh To: CC: , , , , , , , , , Subject: [PATCH] tcp: disable tcp_autocorking for socket when TCP_NODELAY flag is set Date: Mon, 11 Dec 2023 15:58:08 +0000 Message-ID: <20231211155808.14804-1-abuehaze@amazon.com> X-Mailer: git-send-email 2.40.1 In-Reply-To: References: Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain Precedence: Bulk It will be good to submit another version changing the documentation https://docs.kernel.org/networking/timestamping.html editing "It can prevent the situation by always flushing the TCP stack in between requests, for instance by enabling TCP_NODELAY and disabling TCP_CORK and autocork." to "It can prevent the situation by always flushing the TCP stack in between requests, for instance by enabling TCP_NODELAY and disabling TCP_CORK."