From: Leon Romanovsky <leon-2ukJVAZIZ/Y@public.gmane.org>
To: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: Re: vendor extension moratorium?
Date: Wed, 17 Feb 2016 12:02:07 +0200 [thread overview]
Message-ID: <20160217100207.GB30450@leon.nu> (raw)
In-Reply-To: <20160217085508.GA3578-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
On Wed, Feb 17, 2016 at 12:55:08AM -0800, Christoph Hellwig wrote:
> While doing heavy lifting in the RDMA stack I keep running into
> badly designed vendor extensions over and over.
>
> Is there any support for requiring that we'll only add features that
> actually are peer reviewed and standardized before keeping on piling
> up crap? It seems like at least vendors seems to be fighting for death
> by features unfortunately.
Your description of current state is pretty accurate, except one thing -
there are a lot of actively used code in user space with real consumers
which eager to get new features.
Do you have any suggestions on how to handle the adding and exporting
of new IB features?
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-02-17 10:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 8:55 vendor extension moratorium? Christoph Hellwig
[not found] ` <20160217085508.GA3578-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2016-02-17 10:02 ` Leon Romanovsky [this message]
[not found] ` <20160217100207.GB30450-2ukJVAZIZ/Y@public.gmane.org>
2016-02-17 15:05 ` Christoph Hellwig
[not found] ` <20160217150500.GA8164-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2016-02-17 19:18 ` Leon Romanovsky
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=20160217100207.GB30450@leon.nu \
--to=leon-2ukjvaziz/y@public.gmane.org \
--cc=hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.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