On Mon, Apr 04, 2016 at 12:39:29AM -0700, Christoph Hellwig wrote:
> On Wed, Jan 20, 2016 at 01:40:00PM -0600, Faisal Latif wrote:
> > This driver provides iWARP RDMA functionality for the Intel(R) X722 Ethernet
> > controller for PCI Physical Functions. It is in early product cycle
> > and having
On Wed, Jan 20, 2016 at 01:40:00PM -0600, Faisal Latif wrote:
> This driver provides iWARP RDMA functionality for the Intel(R) X722 Ethernet
> controller for PCI Physical Functions. It is in early product cycle
> and having the driver in the kernel will allow users to have hardware support
> when a
From: Or Gerlitz
Date: Thu, 21 Jan 2016 20:40:53 +0200
> On Thu, Jan 21, 2016 at 8:24 PM, Faisal Latif wrote:
>
>> We can certainly take up the discussion on improving the current port mapper
>> design/implementation. But
>> that would be more appropriate in a separate thread.
>
> If we obser
On Thu, Jan 21, 2016 at 8:24 PM, Faisal Latif wrote:
> We can certainly take up the discussion on improving the current port mapper
> design/implementation. But
> that would be more appropriate in a separate thread.
If we observe a kernel API / mechanism which could be wrongly
duplicated betwee
On Thu, Jan 21, 2016 at 07:05:48PM +0200, Or Gerlitz wrote:
> On 1/21/2016 5:32 PM, Steve Wise wrote:
> >Only a single user-space daemon is used.
>
> Good.
>
> >Someone from Intel might have insight into the architecture and design.
> >Perhaps the intention is that individual drivers might want
On 1/21/2016 5:32 PM, Steve Wise wrote:
Only a single user-space daemon is used.
Good.
Someone from Intel might have insight into the architecture and design.
Perhaps the intention is that individual drivers might want to have their own
handlers for these various operations. But currently
> On 1/21/2016 12:57 AM, Steve Wise wrote:
> > I also asked you why the port mapper code has to be present in each
> > iwarp driver and not part of the IB core stack, and you responded
> > "i40iw iwarp driver registers with port mapper and uses its services.
> > Beside that it is not the scope of t
On 1/21/2016 12:57 AM, Steve Wise wrote:
I also asked you why the port mapper code has to be present in each
iwarp driver and not part of the IB core stack, and you responded
"i40iw iwarp driver registers with port mapper and uses its services.
Beside that it is not the scope of the patch series"
> Kirsher; e1000-r...@lists.sourceforge.net
> Subject: Re: [PATCH v3 00/16] add Intel X722 iWARP driver
>
> On Wed, Jan 20, 2016 at 9:40 PM, Faisal Latif wrote:
>
> > Changes since v2:
> [...]
> > *move netlink patch up
>
> I also asked you why
On Wed, Jan 20, 2016 at 9:40 PM, Faisal Latif wrote:
> Changes since v2:
[...]
> *move netlink patch up
I also asked you why the port mapper code has to be present in each
iwarp driver and not part of the IB core stack, and you responded
"i40iw iwarp driver registers with port ma
This driver provides iWARP RDMA functionality for the Intel(R) X722 Ethernet
controller for PCI Physical Functions. It is in early product cycle
and having the driver in the kernel will allow users to have hardware support
when available for purchase.
i40iw cooperates with the Intel(R) X722 base
11 matches
Mail list logo