linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Saleem, Shiraz" <shiraz.saleem@intel.com>
To: Anubhav Guleria <anubhav.nitsri.it@gmail.com>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: RE: Issue with i40iw
Date: Wed, 29 Jul 2020 20:07:56 +0000	[thread overview]
Message-ID: <9DD61F30A802C4429A01CA4200E302A70106600A99@fmsmsx124.amr.corp.intel.com> (raw)
In-Reply-To: <CAFsMY+gFTh_hUDGexx3duLD_anZkar+SNj3S9UhMYH+ciYU-rA@mail.gmail.com>

> Subject: Issue with i40iw
> 
> Hi,
> Both of my servers are running with kernel 4.14.178 and have Intel Ethernet
> Network Adapter X722. Also the IOMMU is disabled. I was trying to run qperf and
> ran into couple of issues:
> 
> 1) While running any bw test, eg. rc_bw or rc_bi_bw, I see following messages in
> dmesg:
> i40iw_cqp_ce_handler: opcode = 0x1 maj_err_code = 0xffff min_err_code =
> 0x8007
> i40iw_wait_event: error cqp command 0xb completion maj = 0xffff min=0x8007
> 
> 2) Following rc benchmarks fail: rc_rdma_write_bw, rc_rdma_write_lat,
> rc_compare_swap_mr, rc_fetch_add_mr, ver_rc_compare_swap and
> ver_rc_fetch_add. For these I get error of failed to post "benchmark name"
> 
> Am I missing something here? Any suggestions?
Are these "rc_compare_swap_mr, rc_fetch_add_mr, ver_rc_compare_swap and
ver_rc_fetch_add" reporting an invalid op code? Those are unsupported in i40iw.

qperf I think uses write with immediate which is also unsupported in i40iw
and could explain the rdma_write_* fails.

For performance benchmarking on x722, we are typically using perftests (ib_* tests)

Shiraz


      reply	other threads:[~2020-07-29 20:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-29 19:54 Issue with i40iw Anubhav Guleria
2020-07-29 20:07 ` Saleem, Shiraz [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=9DD61F30A802C4429A01CA4200E302A70106600A99@fmsmsx124.amr.corp.intel.com \
    --to=shiraz.saleem@intel.com \
    --cc=anubhav.nitsri.it@gmail.com \
    --cc=linux-rdma@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).