From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Moni Shoua <monis-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
Dennis Dalessandro
<dennis.dalessandro-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Ira Weiny <ira.weiny-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Or Gerlitz <gerlitz.or-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Back from PTO
Date: Thu, 21 Jan 2016 14:01:55 -0500 [thread overview]
Message-ID: <56A12B23.6000403@redhat.com> (raw)
In-Reply-To: <CAG9sBKP8kqax_wqyej+1J+hFaaCUFKdFyAX8e4Hxg3HoafWjrg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1778 bytes --]
On 01/19/2016 12:04 PM, Moni Shoua wrote:
> On Mon, Jan 18, 2016 at 11:22 PM, Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
>> rdmavt
>> qib->rdmavt changes
>>
>> Things that I intended to submit after the merge window opened and
>> Greg's merge was done:
>>
>> Retake staging/rdma
>> Delete staging/rdma/{amso1100,ehca,ipath}
>> hfi1->rdmavt changes
>> Add staging/rdma/soft-rxe
>>
> Doug,
> it's not clear if you intend to take rdmavt into drivers/infiniband/sw
I had intended to. However, on Jan 6th at roughly 1pm EST, Dennis
submitted v3 of his rdmavt patch set. At roughly 2pm EST you submitted
a completely different, competing patchset that resides in the same
place in the filesystem, has the same name, but is 100% different
internally. I know Intel and Mellanox have a hard time working
together, but geeze...
> IMHO such a central piece of code needs to go through proper design
> stages, be written with a clear and sharp interface and be published
> with documentation.
Yes, you've repeated this multiple times. As this is a kernel internal
interface only, and a private one to the IB stack, we can be a bit more
flexible than you suggest here and do things a little more on the fly.
> To me it looks like the only purpose of rdmavt is to pull hfi1 driver
> out from staging.
That's obviously the piece that Intel cares about, sure.
> If we want it as an infrastructure for any kind of
> low level driver it needs to stick to infrastructure standards.
This statement is too vague for me to say anything constructive.
> I hope that you agree
Again, too vague to answer.
--
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
GPG KeyID: 0E572FDD
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]
prev parent reply other threads:[~2016-01-21 19:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 21:22 Back from PTO Doug Ledford
[not found] ` <569D57B1.2060205-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-01-19 17:04 ` Moni Shoua
[not found] ` <CAG9sBKP8kqax_wqyej+1J+hFaaCUFKdFyAX8e4Hxg3HoafWjrg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-01-21 19:01 ` Doug Ledford [this message]
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=56A12B23.6000403@redhat.com \
--to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=dennis.dalessandro-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=gerlitz.or-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=ira.weiny-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=monis-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;
as well as URLs for NNTP newsgroup(s).