From: Jakub Kicinski <kuba@kernel.org>
To: Rick Lindsley <ricklind@us.ibm.com>
Cc: netdev@vger.kernel.org, bjking1@linux.ibm.com,
haren@linux.ibm.com, nnac123@linux.ibm.com, mmc@linux.ibm.com
Subject: Re: [PATCH] ibmvnic: Properly dispose of all skbs during a failover.
Date: Thu, 30 Jun 2022 10:52:18 -0700 [thread overview]
Message-ID: <20220630105218.7f23f31c@kernel.org> (raw)
In-Reply-To: <20220630000317.2509347-1-ricklind@us.ibm.com>
On Wed, 29 Jun 2022 17:03:17 -0700 Rick Lindsley wrote:
> During a reset, there may have been transmits in flight that are no
> longer valid and cannot be fulfilled. Resetting and clearing the
> queues is insufficient; each skb also needs to be explicitly freed
> so that upper levels are not left waiting for confirmation of a
> transmit that will never happen. If this happens frequently enough,
> the apparent backlog will cause TCP to begin "congestion control"
> unnecessarily, culminating in permanently decreased throughput.
>
> This was noted during testing of heavy data transfers in
> conjunction with multiple consecutive device failovers.
The indentation in the patch itself is unnecessary, git adds it when
formatting the output of git log (I'm guessing that's the reason you
went this way). Note that the same goes for the subject which looks
padded with spaces from the left.
Please add a Fixes tag pointing at a commit which introduced the
behavior (initial git commit if it's always been there), and repost
with [PATCH net v2] in the subject.
Please keep the review tags you already received when reposting.
prev parent reply other threads:[~2022-06-30 17:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 0:03 [PATCH] ibmvnic: Properly dispose of all skbs during a failover Rick Lindsley
2022-06-30 12:25 ` Brian King
2022-06-30 15:35 ` Nick Child
2022-06-30 17:52 ` Jakub Kicinski [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=20220630105218.7f23f31c@kernel.org \
--to=kuba@kernel.org \
--cc=bjking1@linux.ibm.com \
--cc=haren@linux.ibm.com \
--cc=mmc@linux.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=nnac123@linux.ibm.com \
--cc=ricklind@us.ibm.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;
as well as URLs for NNTP newsgroup(s).