From: Laurence Oberman <loberman@redhat.com>
To: Sagi Grimberg <sagi@grimberg.me>,
Max Gurtovoy <mgurtovoy@nvidia.com>,
David Jeffery <djeffery@redhat.com>
Cc: linux-rdma@vger.kernel.org, target-devel@vger.kernel.org
Subject: Re: [Patch 0/2] iscsit/isert deadlock prevention under heavy I/O
Date: Wed, 16 Mar 2022 11:26:03 -0400 [thread overview]
Message-ID: <a540823d6f3732903080f42a855d2e7cdfc64ade.camel@redhat.com> (raw)
In-Reply-To: <165698e9-9ccd-c840-b926-48f2ee7c6dcb@grimberg.me>
On Wed, 2022-03-16 at 16:39 +0200, Sagi Grimberg wrote:
> Is there any measure-able performance implication?
From our testing and customers it prevented the deadlock, but did not
seem to incur any additional latency. I was reaching similar IOPS/sec
amd GB/sec prior to deadlock.
The benefit seems to be just no more stalls and hung tasks
Thanks for the replies
Kind Regards
Laurence
prev parent reply other threads:[~2022-03-16 15:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 17:57 [Patch 0/2] iscsit/isert deadlock prevention under heavy I/O David Jeffery
2022-03-11 17:57 ` [PATCH 1/2] isert: support for unsolicited NOPIN with no response David Jeffery
2022-03-11 17:57 ` [PATCH 2/2] iscsit: increment max_cmd_sn for isert on command release David Jeffery
2022-03-11 19:08 ` [Patch 0/2] iscsit/isert deadlock prevention under heavy I/O Laurence Oberman
2022-03-13 9:59 ` Max Gurtovoy
2022-03-14 13:57 ` David Jeffery
2022-03-14 14:52 ` Max Gurtovoy
2022-03-14 15:55 ` David Jeffery
2022-03-14 17:40 ` Laurence Oberman
2022-03-16 10:38 ` Max Gurtovoy
2022-03-16 13:07 ` Laurence Oberman
2022-03-16 14:39 ` Sagi Grimberg
2022-03-16 15:26 ` Laurence Oberman [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=a540823d6f3732903080f42a855d2e7cdfc64ade.camel@redhat.com \
--to=loberman@redhat.com \
--cc=djeffery@redhat.com \
--cc=linux-rdma@vger.kernel.org \
--cc=mgurtovoy@nvidia.com \
--cc=sagi@grimberg.me \
--cc=target-devel@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).