MPTCP Linux Development
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Mat Martineau <mathew.j.martineau@linux.intel.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	pabeni@redhat.com, edumazet@google.com,
	matthieu.baerts@tessares.net, mptcp@lists.linux.dev
Subject: Re: [PATCH net-next 0/4] mptcp: Updates for mem scheduling and SK_RECLAIM
Date: Fri, 01 Jul 2022 12:40:15 +0000	[thread overview]
Message-ID: <165667921504.18764.8434604982955394989.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220630221757.763751-1-mathew.j.martineau@linux.intel.com>

Hello:

This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Thu, 30 Jun 2022 15:17:53 -0700 you wrote:
> In the "net: reduce tcp_memory_allocated inflation" series (merge commit
> e10b02ee5b6c), Eric Dumazet noted that "Removal of SK_RECLAIM_CHUNK and
> SK_RECLAIM_THRESHOLD is left to MPTCP maintainers as a follow up."
> 
> Patches 1-3 align MPTCP with the above TCP changes to forward memory
> allocation, reclaim, and memory scheduling.
> 
> [...]

Here is the summary with links:
  - [net-next,1/4] mptcp: never fetch fwd memory from the subflow
    https://git.kernel.org/netdev/net-next/c/4aaa1685f750
  - [net-next,2/4] mptcp: drop SK_RECLAIM_* macros
    https://git.kernel.org/netdev/net-next/c/d24141fe7b48
  - [net-next,3/4] mptcp: refine memory scheduling
    https://git.kernel.org/netdev/net-next/c/69d93daec026
  - [net-next,4/4] net: remove SK_RECLAIM_THRESHOLD and SK_RECLAIM_CHUNK
    https://git.kernel.org/netdev/net-next/c/e918c137db40

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-07-01 12:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-30 22:17 [PATCH net-next 0/4] mptcp: Updates for mem scheduling and SK_RECLAIM Mat Martineau
2022-06-30 22:17 ` [PATCH net-next 1/4] mptcp: never fetch fwd memory from the subflow Mat Martineau
2022-06-30 22:17 ` [PATCH net-next 2/4] mptcp: drop SK_RECLAIM_* macros Mat Martineau
2022-06-30 22:17 ` [PATCH net-next 3/4] mptcp: refine memory scheduling Mat Martineau
2022-06-30 22:17 ` [PATCH net-next 4/4] net: remove SK_RECLAIM_THRESHOLD and SK_RECLAIM_CHUNK Mat Martineau
2022-07-01 12:40 ` patchwork-bot+netdevbpf [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=165667921504.18764.8434604982955394989.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=mathew.j.martineau@linux.intel.com \
    --cc=matthieu.baerts@tessares.net \
    --cc=mptcp@lists.linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox