All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Doug Ledford <dledford@redhat.com>
Cc: Bernard Metzler <bmt@zurich.ibm.com>,
	linux-rdma@vger.kernel.org, jgg@ziepe.ca
Subject: Re: [PATCH v2] Make user mmapped CQ arming flags field 32-bit size to remove 64-bit architecture dependency of siw.
Date: Tue, 13 Aug 2019 13:30:28 +0300	[thread overview]
Message-ID: <20190813103028.GH29138@mtr-leonro.mtl.com> (raw)
In-Reply-To: <a4e4215dab3715e0181fa6c97b583f3feb3d582d.camel@redhat.com>

On Mon, Aug 12, 2019 at 11:17:00AM -0400, Doug Ledford wrote:
> On Fri, 2019-08-09 at 17:18 +0200, Bernard Metzler wrote:
> > This patch changes the driver/user shared (mmapped) CQ notification
> > flags field from unsigned 64-bits size to unsigned 32-bits size. This
> > enables building siw on 32-bit architectures.
> >
> > This patch changes the siw-abi. On previously supported 64-bits
> > little-endian architectures, the old siw user library remains
> > usable, since the used 2 lowest bits of the new 32-bits field reside
> > at the same memory location as those of the old 64-bits field.
> > On 64-bits big-endian systems, the changes would break compatibility.
> > Given the very short time of availability of siw with the current ABI,
> > we do not expect current usage of siw on 64-bit big-endian systems.
> >
> > An according patch to change the siw user library fitting the new ABI
> > will be provided to rdma-core.
>
> I changed the commit message somewhat.  The siw driver was just taken
> into the upstream kernel this merge window, so there is no need to be
> apologetic about abi breakage, there are *no* released kernels with a
> prior abi.  We are only guaranteeing abi compatibility for the official
> siw as taken into the upstream kernel and into rdma-core, and those will
> be kept in sync starting with their first official release, which has
> not yet happened.  Until this rc cycle is complete, we can fix up
> anything that needs fixed up, so if there are any other abi issues you
> think you would like to address, well, chop! chop! ;-)
>
> With that said, thanks, applied to for-rc.
>

Please send relevant change to rdma-core too.

Thanks

  reply	other threads:[~2019-08-13 10:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-09 15:18 [PATCH v2] Make user mmapped CQ arming flags field 32-bit size to remove 64-bit architecture dependency of siw Bernard Metzler
2019-08-12 15:17 ` Doug Ledford
2019-08-13 10:30   ` Leon Romanovsky [this message]
2019-08-13 14:24   ` Bernard Metzler

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=20190813103028.GH29138@mtr-leonro.mtl.com \
    --to=leon@kernel.org \
    --cc=bmt@zurich.ibm.com \
    --cc=dledford@redhat.com \
    --cc=jgg@ziepe.ca \
    --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 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.