From: Yuval Shaia <yuval.shaia@oracle.com>
To: P J P <ppandit@redhat.com>
Cc: Qemu Developers <qemu-devel@nongnu.org>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Saar Amar <saaramar5@gmail.com>, Li Qiang <liq3ea@163.com>,
yuval.shaia@oracle.com
Subject: Re: [Qemu-devel] [PATCH v2 3/6] pvrdma: check number of pages when creating rings
Date: Mon, 17 Dec 2018 21:00:25 +0200 [thread overview]
Message-ID: <20181217190024.GA18696@lap1> (raw)
In-Reply-To: <nycvar.YSQ.7.76.1812180006430.28971@xnncv>
On Tue, Dec 18, 2018 at 12:17:59AM +0530, P J P wrote:
> Hello Yuval,
>
> +-- On Sun, 16 Dec 2018, Yuval Shaia wrote --+
> | With this patch the last step fails, the guest OS hangs, trying to probably
> | unload pvrdma driver and finally gave up after 3 minutes.
>
> Strange...
>
> | Anyways with debug turned on i have noticed that there is one case that
> | devices gets 129 nchunks (i think in MPI) while your patch limits it to 128.
> | >From pvrdma source code we can see that first page is dedicated to ring
> | state, this means that it maybe correct that 128 is the limit but we
> | should check that nchunks does not exceed 129, not 128.
> |
> | What do you think?
>
> -> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/infiniband/hw/vmw_pvrdma/pvrdma_mr.c?id=fdf82a7856b32d905c39afc85e34364491e46346#n201
>
> the vmw_pvrdma kernel driver also seems to set MAX_FAST_REG_PAGE = 128.
So does the user-space library.
Maybe the mr_type is IB_MR_TYPE_MEM_REG.
>
>
> | Ie. to replace this line from create_cq_ring
> | + if (!nchunks || nchunks > PVRDMA_MAX_FAST_REG_PAGES) {
> | with this
> | + if (!nchunks || nchunks > PVRDMA_MAX_FAST_REG_PAGES + 1) {
> |
> | Let me know your opinion.
>
> While it may help to fix the regression. I'm not sure it's a right fix.
> 129 seems a little odd number to have as limit.
Agree, let's stick with this patch.
>
> Is it possible MPI is erring in getting 129 chunks?
Yeah but still the driver is holding the shutdown, not MPI.
Anyways, I found a wrong setting of respose to driver in "Add support for
RDMA MAD" patchset v6 and fixed that.
Now the regression is fine, i.e. VM goes down smoothly.
>
> IMO it's better to confirm the right value for 'MAX_FAST_REG_PAGES', before
> going with > PVRDMA_MAX_FAS_REG_PAGES(=128) + 1.
Agree.
>
> Thank you.
> --
> Prasad J Pandit / Red Hat Product Security Team
> 47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F
next prev parent reply other threads:[~2018-12-17 19:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 19:30 [Qemu-devel] [PATCH v2 0/6] rdma: various issues in rdma/pvrdma backend P J P
2018-12-12 19:30 ` [Qemu-devel] [PATCH v2 1/6] rdma: check num_sge does not exceed MAX_SGE P J P
2018-12-12 19:30 ` [Qemu-devel] [PATCH v2 2/6] pvrdma: add uar_read routine P J P
2018-12-13 8:42 ` Marcel Apfelbaum
2018-12-12 19:30 ` [Qemu-devel] [PATCH v2 3/6] pvrdma: check number of pages when creating rings P J P
2018-12-16 20:30 ` Yuval Shaia
2018-12-17 18:47 ` P J P
2018-12-17 19:00 ` Yuval Shaia [this message]
2018-12-12 19:30 ` [Qemu-devel] [PATCH v2 4/6] pvrdma: release ring object in case of an error P J P
2018-12-12 19:30 ` [Qemu-devel] [PATCH v2 5/6] rdma: remove unused VENDOR_ERR_NO_SGE macro P J P
2018-12-13 5:19 ` Yuval Shaia
2018-12-12 19:30 ` [Qemu-devel] [PATCH v2 6/6] pvrdma: check return value from pvrdma_idx_ring_has_ routines P J P
2018-12-13 5:22 ` Yuval Shaia
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=20181217190024.GA18696@lap1 \
--to=yuval.shaia@oracle.com \
--cc=liq3ea@163.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=ppandit@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=saaramar5@gmail.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.