All of lore.kernel.org
 help / color / mirror / Atom feed
From: Haris Iqbal <haris.iqbal@ionos.com>
To: Guoqing Jiang <guoqing.jiang@linux.dev>
Cc: RDMA mailing list <linux-rdma@vger.kernel.org>,
	yanjun.zhu@linux.dev, Jinpu Wang <jinpu.wang@ionos.com>
Subject: Re: Encountering errors while using RNBD over rxe for v5.14
Date: Wed, 4 May 2022 16:22:54 +0200	[thread overview]
Message-ID: <CAJpMwyhuOOgub4xxd6nB64c37yC82ogZCX4LB6WkUb721odLjQ@mail.gmail.com> (raw)
In-Reply-To: <95d12c5b-83bb-dce6-750a-3827118b9aaf@linux.dev>

Hi Guoqing,

On Fri, Apr 29, 2022 at 10:26 AM Guoqing Jiang <guoqing.jiang@linux.dev> wrote:
>
> Hi Haris,
>
> On 4/20/22 6:28 PM, Haris Iqbal wrote:
> > Hello,
> >
> > We are facing some issues with the rxe driver in v5.14 (tested with 5.14.21)
> >
> > After mapping a single RNBD device with 2 rxe interfaces, and with the
> > below fio config,
> >
> > [global]
> > description=Emulation of Storage Server Access Pattern
> > bssplit=512/20:1k/16:2k/9:4k/12:8k/19:16k/10:32k/8:64k/4
> > fadvise_hint=0
> > rw=randrw:2
> > direct=1
> > random_distribution=zipf:1.2
> > time_based=1
> > runtime=60
> > ramp_time=1
> > ioengine=libaio
> > iodepth=128
> > iodepth_batch_submit=128
> > iodepth_batch_complete_min=1
> > iodepth_batch_complete_max=128
> > numjobs=1
> > group_reporting
> >
> > [job1]
> > filename=/dev/rnbd0
> >
> >
> > We observe the following error,
> >
> > [Fri Mar 25 19:08:03 2022] rtrs_client L353: <blya>: Failed
> > IB_WR_LOCAL_INV: WR flushed
> > [Fri Mar 25 19:08:03 2022] rtrs_client L333: <blya>: Failed
> > IB_WR_REG_MR: WR flushed
> > [Fri Mar 25 19:08:03 2022] rtrs_client L333: <blya>: Failed
> > IB_WR_REG_MR: WR flushed
> > [Fri Mar 25 19:08:34 2022] rtrs_client L353: <blya>: Failed
> > IB_WR_LOCAL_INV: WR flushed
> > [Fri Mar 25 19:08:34 2022] rtrs_client L353: <blya>:*Failed IB_WR_LOCAL_INV: WR flushed*
>
> I got similar message but I am not certain it is the same one, pls see
> the previous report,
>
> https://lore.kernel.org/linux-rdma/20220210073655.42281-1-guoqing.jiang@linux.dev/

I went through the emails, and the error looks similar but I am not
sure if its related. The change to write_lock_bh was done after v5.14
I think, and the code where I am seeing this error still has irq
versions of those lock (e.g. write_lock_irqsave).

I don't have much knowledge of rxe code, hence I cannot really say for sure.

Thanks for the response.

>
> Thanks,
> Guoqing

  reply	other threads:[~2022-05-04 14:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-20 10:28 Encountering errors while using RNBD over rxe for v5.14 Haris Iqbal
2022-04-27 11:49 ` Haris Iqbal
2022-04-29  8:26 ` Guoqing Jiang
2022-05-04 14:22   ` Haris Iqbal [this message]
2022-05-05  3:46     ` Guoqing Jiang
2022-05-05 11:20       ` Haris Iqbal

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=CAJpMwyhuOOgub4xxd6nB64c37yC82ogZCX4LB6WkUb721odLjQ@mail.gmail.com \
    --to=haris.iqbal@ionos.com \
    --cc=guoqing.jiang@linux.dev \
    --cc=jinpu.wang@ionos.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=yanjun.zhu@linux.dev \
    /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.