From: Jason Gunthorpe <jgg@ziepe.ca>
To: Gal Pressman <galpress@amazon.com>
Cc: Dennis Dalessandro <dennis.dalessandro@intel.com>,
Leon Romanovsky <leon@kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Honggang LI <honli@redhat.com>
Subject: Re: RDMA device renames and node description
Date: Wed, 19 Feb 2020 12:54:23 -0400 [thread overview]
Message-ID: <20200219165423.GR31668@ziepe.ca> (raw)
In-Reply-To: <67915d24-149a-e940-1f0b-a173eb4aca84@amazon.com>
On Wed, Feb 19, 2020 at 04:35:40PM +0200, Gal Pressman wrote:
> > Again, call it what you want, but you can't deny this change to force the rename
> > by default has not broken things. For the record I'm not even talking about PSM2
> > here. There are other, more far reaching implications.
>
> It's not just PSM2, it broke our libfabric provider and apparently MVAPICH as well:
> http://mailman.cse.ohio-state.edu/pipermail/mvapich-discuss/2020-January/006960.html
You all recognize that finding stuff name dependent stuff like this is
horribly hacky, right?
The whole point of doing this, over a long time, is to get all this
hacky stuff fixed up.
> Regarding the issue you described, why not disable the rename on the upgrade
> path and only enable it for fresh installations?
That isn't really a rdma-core issue, though?
Jason
next prev parent reply other threads:[~2020-02-19 16:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 18:13 RDMA device renames and node description Dennis Dalessandro
2020-02-18 14:04 ` Leon Romanovsky
2020-02-18 17:11 ` Dennis Dalessandro
2020-02-18 20:08 ` Jason Gunthorpe
2020-02-19 7:11 ` Leon Romanovsky
2020-02-19 14:14 ` Dennis Dalessandro
2020-02-19 14:35 ` Gal Pressman
2020-02-19 15:10 ` Leon Romanovsky
2020-02-19 16:54 ` Jason Gunthorpe [this message]
2020-02-19 14:48 ` Leon Romanovsky
2020-02-19 15:34 ` Dennis Dalessandro
2020-02-19 16:58 ` Jason Gunthorpe
2020-02-19 19:35 ` Dennis Dalessandro
2020-02-19 23:18 ` Ira Weiny
2020-02-20 2:26 ` Dennis Dalessandro
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=20200219165423.GR31668@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=dennis.dalessandro@intel.com \
--cc=galpress@amazon.com \
--cc=honli@redhat.com \
--cc=leon@kernel.org \
--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 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).