From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: sagi grimberg <sagig@mellanox.com>,
"tony.seo@samsung.com" <tony.seo@samsung.com>,
Alex Leung <Alex.Leung@Emulex.Com>,
"Nicholas A. Bellinger" <nab@linux-iscsi.org>,
target-devel <target-devel@vger.kernel.org>,
Or Gerlitz <ogerlitz@mellanox.com>, Oren Duer <oren@mellanox.com>,
linux-rdma@vger.kernel.org
Subject: Re: isert for mellanox drivers
Date: Thu, 24 Apr 2014 23:55:08 -0600 [thread overview]
Message-ID: <20140425055508.GB23896@obsidianresearch.com> (raw)
In-Reply-To: <20140425053825.GB9435@infradead.org>
On Thu, Apr 24, 2014 at 10:38:25PM -0700, Christoph Hellwig wrote:
> On Thu, Apr 24, 2014 at 12:54:40PM +0300, sagi grimberg wrote:
> > Well, I feel the same way (although less harsh about it), I would
> > prefer to have it all inbox.
> > As I see it, OFED is useful for costumers who want to upgrade RDMA
> > functionality (or get Tech previews)
> > without upgrading their distro or wait for it to land upstream.
>
> For that we have the compat drivers project, which could easily handle
> the rdma drivers as well.
>
> The problem with OFED is (or was last time a looked) that it's a big
> pile that includes backports, and new features not submitted or even
> rejected upstream.
Official OFA OFED is now strictly backports from a given kernel
verison, and TBH, is not widely used now that everything is included
in the modern distros.
The vendor 'OFEDs' remain a big pile. I'm not even sure source is
proved for them.. At least it isn't readily apparent.
IMHO, the vendors should not be co-opting the OFED branding, but that
is a whole other topic....
Jason
next prev parent reply other threads:[~2014-04-25 5:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5DD781F004516D4BBC46D51FA58794102D464FFB@CMEXMB1.ad.emulex.com>
[not found] ` <5358B396.4060904@mellanox.com>
[not found] ` <20140424070804.GA20442@infradead.org>
[not found] ` <5358DF60.9010202@mellanox.com>
2014-04-25 5:38 ` isert for mellanox drivers Christoph Hellwig
2014-04-25 5:55 ` Jason Gunthorpe [this message]
2014-04-25 6:03 ` Christoph Hellwig
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=20140425055508.GB23896@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=Alex.Leung@Emulex.Com \
--cc=hch@infradead.org \
--cc=linux-rdma@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=ogerlitz@mellanox.com \
--cc=oren@mellanox.com \
--cc=sagig@mellanox.com \
--cc=target-devel@vger.kernel.org \
--cc=tony.seo@samsung.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