ehca driver status?

ehca driver status?

[Christoph Hellwig]

Hi Hoang-Nam, hi Christoph, hi Alexander,

do you know what the current state of the eHCA driver and hardware is?

The driver hasn't seen any targeted updats since 2010, so we wonder if
it's still alive?  It's one of the few drivers not supporting FRWRs,
and it's also really odd in that it has its own dma_map_ops
implementation that seems to pass virtual addresses to the hardware (or
probably rather firmware), getting in the way of at least two currently
pending cleanups.
--
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

Re: ehca driver status?

[Alexander Schmidt]

On Wed, 26 Aug 2015 06:46:48 -0700
Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org> wrote:

> Hi Hoang-Nam, hi Christoph, hi Alexander,
> 
> do you know what the current state of the eHCA driver and hardware is?
> 
> The driver hasn't seen any targeted updats since 2010, so we wonder if
> it's still alive?  It's one of the few drivers not supporting FRWRs,
> and it's also really odd in that it has its own dma_map_ops
> implementation that seems to pass virtual addresses to the hardware
> (or probably rather firmware), getting in the way of at least two
> currently pending cleanups.
> 

Hi Christoph,

I'll try to find out if we still need the device driver in the
kernel tree. It will take 2-3 weeks because the key people are on
vacation right now, but I'll get back to you.

Regards,
Alex

--
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

Re: ehca driver status?

[Alexander Schmidt]

On Wed, 26 Aug 2015 06:46:48 -0700
Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org> wrote:

> Hi Hoang-Nam, hi Christoph, hi Alexander,
> 
> do you know what the current state of the eHCA driver and hardware is?
> 
> The driver hasn't seen any targeted updats since 2010, so we wonder if
> it's still alive?  It's one of the few drivers not supporting FRWRs,
> and it's also really odd in that it has its own dma_map_ops
> implementation that seems to pass virtual addresses to the hardware
> (or probably rather firmware), getting in the way of at least two
> currently pending cleanups.
> 

Hi again,

we are okay with removing the driver from the tree, let me know if
there is anything we should do to help.

Regards,
Alex

--
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

Re: ehca driver status?

[Doug Ledford]

[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]

On 09/11/2015 04:55 AM, Alexander Schmidt wrote:
> On Wed, 26 Aug 2015 06:46:48 -0700
> Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org> wrote:
> 
>> Hi Hoang-Nam, hi Christoph, hi Alexander,
>>
>> do you know what the current state of the eHCA driver and hardware is?
>>
>> The driver hasn't seen any targeted updats since 2010, so we wonder if
>> it's still alive?  It's one of the few drivers not supporting FRWRs,
>> and it's also really odd in that it has its own dma_map_ops
>> implementation that seems to pass virtual addresses to the hardware
>> (or probably rather firmware), getting in the way of at least two
>> currently pending cleanups.
>>
> 
> Hi again,
> 
> we are okay with removing the driver from the tree, let me know if
> there is anything we should do to help.

I'll get it moved over to staging ASAP so it can be on the same schedule
as the other two drivers we are deprecating.  Thanks!


-- 
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
              GPG KeyID: 0E572FDD



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]