On 9/1/2016 2:14 PM, Jason Gunthorpe wrote:
> On Thu, Sep 01, 2016 at 02:03:52PM +0300, Leon Romanovsky wrote:
>> On Thu, Sep 01, 2016 at 01:26:43AM -0700, Christoph Hellwig wrote:
>>> Arguing with these sorts of bullshit positions from Robert and Leon
>>> just makes me feel tired.
>>
>> What are you arguing with us about? These "clueless" people suggested
>> you the way to move forward and get vendor support to this effort -
>> convince Doug to add co-maintainer to RDMA stack (kernel and user-space) to
>> help him to deal with increase in upstream activity.
>>
>> This co-maintainer won't deal with API's patches (UAPI and libibverbs),
>> but will help with various internal things (drivers, user-space drivers,
>> ulps, fixes, e.t.c).
>>
>> The kernel.org infrastructure allows multiple write access to the same
>> repository and there are subsystems which are already using it.
>>
>> If it helps, I can step in and do this job.
>
> I certainly keep hearing a call for a more team oriented approach with
> our maintainership, and to me it makes sense that the same basic team
> steward the kernel and user plumbing. So I'm supportive of the idea.
>
> I'm less concerned with speed and more with reliablity when Doug is
> unavailable and to make sure we are developing community and expertise
> in a wider group of people.. The work load only seems to be increasing,
> we've hand an unprecedented number of new provider drivers this year.
And there are more coming. I had a private discussion with someone just
last night as a matter of fact. It went something like this:
Them: I have a new driver to submit, I think I can have it on list in a
few days, will that be possible to make 4.9?
Me: I doubt it's even possible at this point. Even if you did
everything perfect, there have been so many submissions, and a couple or
three drivers are already on the list waiting inclusion ahead of you,
that I just don't think it's possible to review it in that timeframe.
> Doug? This is the sort of discussion I think you need to be leading.
I'm going to think about this for a bit...more later today...
--
Doug Ledford <dledford@xxxxxxxxxx>
GPG Key ID: 0E572FDD
Attachment:
signature.asc
Description: OpenPGP digital signature
