From: Ming Lei <ming.lei@redhat.com>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
linux-rdma@vger.kernel.org, Max Gurtovoy <maxg@mellanox.com>,
Stephen Rust <srust@blockbridge.com>,
Doug Dumitru <doug@dumitru.com>
Subject: Re: [PATCH] IB/isert: fix unaligned immediate-data handling
Date: Tue, 1 Sep 2020 09:00:46 +0800 [thread overview]
Message-ID: <20200901010046.GA289251@T590> (raw)
In-Reply-To: <8bc2755b-e7d6-5d9c-f5e0-e8036b28beb6@grimberg.me>
On Mon, Aug 31, 2020 at 09:48:12AM -0700, Sagi Grimberg wrote:
>
> > > Currently we allocate rx buffers in a single contiguous buffers
> > > for headers (iser and iscsi) and data trailer. This means
> > > that most likely the data starting offset is aligned to 76
> > > bytes (size of both headers).
> > >
> > > This worked fine for years, but at some point this broke.
> > > To fix this, we should avoid passing unaligned buffers for
> > > I/O.
> >
> > That is a bit vauge - what suddenly broke it?
>
> Somewhere around the multipage bvec work that Ming did. The issue was
> that brd assumed a 512 aligned page vector. IIRC the discussion settled
> that the block layer expects a 512B aligned buffer(s).
I don't think the limit is from multipage bvec, and the limit is
actually from driver since block layer just sets up the vectors which
is passed to driver, see the following discussion:
https://lore.kernel.org/linux-block/20191204230225.GA26189@ming.t460p/
So what is the exact setting for reproducing the issue? Some underlying
driver does require aligned buffer, such as loop/dio, brd, or when kasan
is involved for buffer allocated via kmalloc().
Thanks,
Ming
next prev parent reply other threads:[~2020-09-01 1:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-30 10:32 [PATCH] IB/isert: fix unaligned immediate-data handling Sagi Grimberg
2020-08-31 5:14 ` Christoph Hellwig
2020-08-31 5:37 ` Doug Dumitru
2020-08-31 12:18 ` Jason Gunthorpe
2020-08-31 16:29 ` Doug Dumitru
2020-08-31 16:48 ` Sagi Grimberg
[not found] ` <CAAFE1bcXNdMD5AR80tSFVoYouTrEg_swR73ba2FVEB5UH7MXLQ@mail.gmail.com>
2020-08-31 16:59 ` Stephen Rust
2020-08-31 17:02 ` Doug Dumitru
2020-08-31 17:59 ` Jason Gunthorpe
2020-09-01 5:56 ` Christoph Hellwig
2020-09-01 7:42 ` Sagi Grimberg
2020-09-01 1:00 ` Ming Lei [this message]
2020-09-01 1:10 ` Sagi Grimberg
2020-09-01 2:01 ` Ming Lei
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=20200901010046.GA289251@T590 \
--to=ming.lei@redhat.com \
--cc=doug@dumitru.com \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--cc=maxg@mellanox.com \
--cc=sagi@grimberg.me \
--cc=srust@blockbridge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox