All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Rohit Nair <rohit.sajan.kumar@oracle.com>
Cc: jgg@ziepe.ca, saeedm@nvidia.com, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, manjunath.b.patil@oracle.com,
	rama.nichanamatlu@oracle.com,
	Michael Guralnik <michaelgur@nvidia.com>
Subject: Re: [External] : Re: [PATCH 1/1] IB/mlx5: Add a signature check to received EQEs and CQEs
Date: Sun, 6 Nov 2022 20:03:00 +0200	[thread overview]
Message-ID: <Y2f21JKWkQg8KtyK@unreal> (raw)
In-Reply-To: <fdb9f874-1998-5270-4360-61c74c34294d@oracle.com>

On Fri, Oct 28, 2022 at 04:48:53PM -0700, Rohit Nair wrote:
> On 10/27/22 5:23 AM, Leon Romanovsky wrote:
> > On Tue, Oct 25, 2022 at 10:44:12AM -0700, Rohit Nair wrote:
> > > Hey Leon,
> > > 
> > > Please find my replies to your comments here below:
> > 
> > <...>
> > 
> > > > 
> > > > > This patch does not introduce any significant performance degradations
> > > > > and has been tested using qperf.
> > > > What does it mean? You made changes in kernel verbs flow, they are not
> > > > executed through qperf.
> > > We also conducted several extensive performance tests using our test-suite
> > > which utilizes rds-stress and also saw no significant performance
> > > degrdations in those results.
> > 
> > What does it mean "also"? Your change is applicable ONLY for kernel path.
> > 
> > Anyway, I'm not keen adding rare debug code to performance critical path.
> > 
> > Thanks
> 
> rds-stress exercises the codepath we are modifying here. rds-stress didn't
> show much of performance degrade when we ran internally. We also requested
> our DB team for performance regression testing and this change passed their
> test suite. This motivated us to submit this to upstream.
> 
> If there is any other test that is better suited for this change, I am
> willing to test it. Please let me know if you have something in mind. We can
> revisit this patch after such a test may be.
> 
> I agree that, this was a rare debug scenario, but it took lot more than
> needed to narrow down[engaged vendor on live sessions]. We are adding this
> in the hope to finding the cause at the earliest or at least point us which
> direction to look at. We also requested the vendor[mlx] to include some
> diagnostics[HW counter], which can help us narrow it faster next time. This
> is our attempt to add kernel side of diagnostics.

The thing is that "vendor" failed to explain internally if this debug
code is useful. Like I said, extremely rare debug code shouldn't be part
of main data path.

Thanks

> 
> Feel free to share your suggestions
> 
> Thanks
> 

  reply	other threads:[~2022-11-06 18:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-05 17:45 [PATCH 1/1] IB/mlx5: Add a signature check to received EQEs and CQEs Rohit Nair
2022-10-11  7:17 ` Leon Romanovsky
2022-10-25 17:44   ` [External] : " Rohit Nair
2022-10-27 12:23     ` Leon Romanovsky
2022-10-28 23:48       ` Rohit Nair
2022-11-06 18:03         ` Leon Romanovsky [this message]
2022-11-07 17:51           ` Rohit Nair
     [not found]           ` <f3a56720-4df4-6b17-bfdf-4385dc27a2c0@oracle.com>
2022-11-09 18:33             ` Leon Romanovsky

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=Y2f21JKWkQg8KtyK@unreal \
    --to=leon@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jgg@ziepe.ca \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=manjunath.b.patil@oracle.com \
    --cc=michaelgur@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rama.nichanamatlu@oracle.com \
    --cc=rohit.sajan.kumar@oracle.com \
    --cc=saeedm@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.