From: Doug Ledford <dledford@redhat.com>
To: Dennis Dalessandro <dennis.dalessandro@intel.com>, jgg@ziepe.ca
Cc: linux-rdma@vger.kernel.org,
Mike Marciniszyn <mike.marciniszyn@intel.com>,
stable@vger.kernel.org, Kaike Wan <kaike.wan@intel.com>
Subject: Re: [PATCH for-rc 1/2] IB/hfi1: Avoid excessive retry for TID RDMA READ request
Date: Thu, 17 Oct 2019 16:34:20 -0400 [thread overview]
Message-ID: <0af4756e60b72629cad79e93ce7f0c8a8451f116.camel@redhat.com> (raw)
In-Reply-To: <20191004204035.26542.41684.stgit@awfm-01.aw.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1955 bytes --]
On Fri, 2019-10-04 at 16:40 -0400, Dennis Dalessandro wrote:
> From: Kaike Wan <kaike.wan@intel.com>
>
> A TID RDMA READ request could be retried under one of the following
> conditions:
> - The RC retry timer expires;
> - A later TID RDMA READ RESP packet is received before the next
> expected one.
> For the latter, under normal conditions, the PSN in IB space is used
> for comparison. More specifically, the IB PSN in the incoming TID RDMA
> READ RESP packet is compared with the last IB PSN of a given TID RDMA
> READ request to determine if the request should be retried. This is
> similar to the retry logic for noraml RDMA READ request.
>
> However, if a TID RDMA READ RESP packet is lost due to congestion,
> header suppresion will be disabled and each incoming packet will raise
> an interrupt until the hardware flow is reloaded. Under this
> condition,
> each packet KDETH PSN will be checked by software against r_next_psn
> and a retry will be requested if the packet KDETH PSN is later than
> r_next_psn. Since each TID RDMA READ segment could have up to 64
> packets and each TID RDMA READ request could have many segments, we
> could make far more retries under such conditions, and thus leading to
> RETRY_EXC_ERR status.
>
> This patch fixes the issue by removing the retry when the incoming
> packet KDETH PSN is later than r_next_psn. Instead, it resorts to
> RC timer and normal IB PSN comparison for any request retry.
>
> Fixes: 9905bf06e890 ("IB/hfi1: Add functions to receive TID RDMA READ
> response")
> Cc: <stable@vger.kernel.org>
> Reviewed-by: Mike Marciniszyn <mike.marciniszyn@intel.com>
> Signed-off-by: Kaike Wan <kaike.wan@intel.com>
> Signed-off-by: Dennis Dalessandro <dennis.dalessandro@intel.com>
Thanks, applied to for-rc.
--
Doug Ledford <dledford@redhat.com>
GPG KeyID: B826A3330E572FDD
Fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-10-17 20:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191004203739.26542.57060.stgit@awfm-01.aw.intel.com>
2019-10-04 20:40 ` [PATCH for-rc 1/2] IB/hfi1: Avoid excessive retry for TID RDMA READ request Dennis Dalessandro
2019-10-17 20:34 ` Doug Ledford [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=0af4756e60b72629cad79e93ce7f0c8a8451f116.camel@redhat.com \
--to=dledford@redhat.com \
--cc=dennis.dalessandro@intel.com \
--cc=jgg@ziepe.ca \
--cc=kaike.wan@intel.com \
--cc=linux-rdma@vger.kernel.org \
--cc=mike.marciniszyn@intel.com \
--cc=stable@vger.kernel.org \
/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).