From: Leon Romanovsky <leon@kernel.org>
To: Gal Pressman <galpress@amazon.com>
Cc: Shiraz Saleem <shiraz.saleem@intel.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
Doug Ledford <dledford@redhat.com>,
linux-rdma@vger.kernel.org,
Alexander Matushevsky <matua@amazon.com>,
stable@vger.kernel.org, "Leybovich, Yossi" <sleybo@amazon.com>
Subject: Re: [PATCH for-rc] Revert "RDMA/efa: Use API to get contiguous memory blocks aligned to device supported page size"
Date: Thu, 23 Jan 2020 16:24:43 +0200 [thread overview]
Message-ID: <20200123142443.GN7018@unreal> (raw)
In-Reply-To: <47c20471-2251-b93b-053d-87880fa0edf5@amazon.com>
On Wed, Jan 22, 2020 at 09:57:07AM +0200, Gal Pressman wrote:
> On 21/01/2020 18:24, Leon Romanovsky wrote:
> > On Tue, Jan 21, 2020 at 11:07:21AM +0200, Gal Pressman wrote:
> >> On 20/01/2020 16:10, Gal Pressman wrote:
> >>> The cited commit leads to register MR failures and random hangs when
> >>> running different MPI applications. The exact root cause for the issue
> >>> is still not clear, this revert brings us back to a stable state.
> >>>
> >>> This reverts commit 40ddb3f020834f9afb7aab31385994811f4db259.
> >>>
> >>> Fixes: 40ddb3f02083 ("RDMA/efa: Use API to get contiguous memory blocks aligned to device supported page size")
> >>> Cc: Shiraz Saleem <shiraz.saleem@intel.com>
> >>> Cc: stable@vger.kernel.org # 5.3
> >>> Signed-off-by: Gal Pressman <galpress@amazon.com>
> >>
> >> Shiraz, I think I found the root cause here.
> >> I'm noticing a register MR of size 32k, which is constructed from two sges, the
> >> first sge of size 12k and the second of 20k.
> >>
> >> ib_umem_find_best_pgsz returns page shift 13 in the following way:
> >>
> >> 0x103dcb2000 0x103dcb5000 0x103dd5d000 0x103dd62000
> >> +----------+ +------------------+
> >> | | | |
> >> | 12k | | 20k |
> >> +----------+ +------------------+
> >>
> >> +------+------+ +------+------+------+
> >> | | | | | | |
> >> | 8k | 8k | | 8k | 8k | 8k |
> >> +------+------+ +------+------+------+
> >> 0x103dcb2000 0x103dcb6000 0x103dd5c000 0x103dd62000
> >>
> >>
> >> The top row is the original umem sgl, and the bottom is the sgl constructed by
> >> rdma_for_each_block with page size of 8k.
> >>
> >> Is this the expected output? The 8k pages cover addresses which aren't part of
> >> the MR. This breaks some of the assumptions in the driver (for example, the way
> >> we calculate the number of pages in the MR) and I'm not sure our device can
> >> handle such sgl.
> >
> > Artemy wrote this fix that can help you.
> >
> > commit 60c9fe2d18b657df950a5f4d5a7955694bd08e63
> > Author: Artemy Kovalyov <artemyko@mellanox.com>
> > Date: Sun Dec 15 12:43:13 2019 +0200
> >
> > RDMA/umem: Fix ib_umem_find_best_pgsz()
> >
> > Except for the last entry, the ending iova alignment sets the maximum
> > possible page size as the low bits of the iova must be zero when
> > starting the next chunk.
> >
> > Fixes: 4a35339958f1 ("RDMA/umem: Add API to find best driver supported page size in an MR")
> > Signed-off-by: Artemy Kovalyov <artemyko@mellanox.com>
> > Signed-off-by: Leon Romanovsky <leonro@mellanox.com>
> >
> > diff --git a/drivers/infiniband/core/umem.c b/drivers/infiniband/core/umem.c
> > index c3769a5f096d..06b6125b5ae1 100644
> > --- a/drivers/infiniband/core/umem.c
> > +++ b/drivers/infiniband/core/umem.c
> > @@ -166,10 +166,13 @@ unsigned long ib_umem_find_best_pgsz(struct ib_umem *umem,
> > * for any address.
> > */
> > mask |= (sg_dma_address(sg) + pgoff) ^ va;
> > - if (i && i != (umem->nmap - 1))
> > - /* restrict by length as well for interior SGEs */
> > - mask |= sg_dma_len(sg);
> > va += sg_dma_len(sg) - pgoff;
> > + /* Except for the last entry, the ending iova alignment sets
> > + * the maximum possible page size as the low bits of the iova
> > + * must be zero when starting the next chunk.
> > + */
> > + if (i != (umem->nmap - 1))
> > + mask |= va;
> > pgoff = 0;
> > }
> > best_pg_bit = rdma_find_pg_bit(mask, pgsz_bitmap);
>
> Thanks Leon, I'll test this and let you know if it fixes the issue.
> When are you planning to submit this?
If it fixes your issues, I will be happy to do it.
Thanks
next prev parent reply other threads:[~2020-01-23 14:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 14:10 [PATCH for-rc] Revert "RDMA/efa: Use API to get contiguous memory blocks aligned to device supported page size" Gal Pressman
2020-01-21 9:07 ` Gal Pressman
2020-01-21 16:24 ` Leon Romanovsky
2020-01-22 7:57 ` Gal Pressman
2020-01-23 14:24 ` Leon Romanovsky [this message]
2020-01-23 14:29 ` Gal Pressman
2020-01-24 0:40 ` Saleem, Shiraz
2020-01-24 2:52 ` Jason Gunthorpe
2020-01-28 12:32 ` Gal Pressman
2020-01-28 13:47 ` Leon Romanovsky
2020-01-21 16:39 ` Saleem, Shiraz
2020-01-22 7:58 ` Gal Pressman
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=20200123142443.GN7018@unreal \
--to=leon@kernel.org \
--cc=dledford@redhat.com \
--cc=galpress@amazon.com \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--cc=matua@amazon.com \
--cc=shiraz.saleem@intel.com \
--cc=sleybo@amazon.com \
--cc=stable@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).