From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (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 E44EE4A23 for ; Fri, 29 Jul 2022 15:33:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1659108834; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=VPFpAlxZ1Fqq+8efVjPI2mRPaSb57UfRdPk9P1KQSjc=; b=XowTIOiIK1D4hAEjXGEbTtWS70e8j4W2scZJC3dh/yPqF5UTG1Kx3NE9IdgIOQGw9tRCae +Xc3TWtEelOF3YutaRs5aMdUnCCL6i9LtS+JqsH5lUBXLboiaiXYGoT+gj6/DUUVC3eVfX vMUCLefkzS4WZYu95GD6Sh7YsVuZD/4= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-21-dTip1z4qOsWCnxhIKf68Rg-1; Fri, 29 Jul 2022 11:33:52 -0400 X-MC-Unique: dTip1z4qOsWCnxhIKf68Rg-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 76BFC101A54E for ; Fri, 29 Jul 2022 15:33:52 +0000 (UTC) Received: from gerbillo.redhat.com (unknown [10.39.192.205]) by smtp.corp.redhat.com (Postfix) with ESMTP id 0752C90A04 for ; Fri, 29 Jul 2022 15:33:51 +0000 (UTC) From: Paolo Abeni To: mptcp@lists.linux.dev Subject: [PATCH mptcp-next 0/4] mptcp: just another receive path refactor Date: Fri, 29 Jul 2022 17:33:00 +0200 Message-Id: Precedence: bulk X-Mailing-List: mptcp@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.11.54.5 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=pabeni@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="US-ASCII"; x-default=true This is a refresh and rebase of an already shared work: https://lore.kernel.org/mptcp/cover.1621963632.git.pabeni@redhat.com/ [1] The motiviation for refreshing this is: https://lore.kernel.org/mptcp/YtVhyGSsv1CWvPz4@xsang-OptiPlex-9020/ specifically it looks like that properly attaching mem_cg to the msk socket would be (much?) easier if the RX path and the fwd memory allocation would be under msk socket lock protection. The first 2 patches are proably worthy even without the refactor, but specifically the 2nd one is required to get a good mptcp-level acking behavior when we move the rx under the socket lock. The 3rd patch does the real work, and the 4th is a follow-up cleanup. Back at [1], I measured relevant performance regressions in some specific cases. I've done the same test here and I now see little to noise changes. I guess that is mostly due to the better acking strategy already introduce with commit 949dfdcf343c ("Merge branch 'mptcp-improve-mptcp-level-window-tracking'") and refined here. Paolo Abeni (4): mptcp: move RCVPRUNE event later mptcp: more accurate receive buffer updates mptcp: move msk input path under full msk socket lock mptcp: use common helper for rmem memory accounting include/net/mptcp.h | 2 + net/ipv4/tcp.c | 3 + net/mptcp/options.c | 1 - net/mptcp/protocol.c | 220 +++++++++++-------------------------------- net/mptcp/protocol.h | 12 ++- 5 files changed, 69 insertions(+), 169 deletions(-) -- 2.35.3