[lkml]   [2006]   [Dec]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v2 04/13] Connection Manager
On Tue, Dec 05, 2006 at 09:39:58AM -0600, Steve Wise ( wrote:
> > Phrases like "MPA-aware TCP" rises a lot of questions - briefly saying
> > that hardware (even if it is called ethernet driver) can create and work
> > with own TCP flows potentially modified in the way it likes which is seen
> > in driver. Likely such flows will not be seen by upper layers like OS
> > network stack according to hardware descriptions.
> >
> > Is it correct?
> >
> I don't quite get your point about the driver aspect of this?
> The HW manages the iWARP connection including data flow. It adheres to
> the MPA, RDDP, and RDMAP protocol specification IDs from the IETF. The
> HW manages how data gets pushed out in the RDMA stream. The RDMA
> Driver just requests a TCP connection and does the MPA exchange. Then
> tells the hardware to move the connection into RDMA mode. From that
> point on, the driver simply suffles IO work requests from the consumer
> application to the hardware and handles asynchronous events while the
> connection is up and running.

My main concern about this is the fact, that protocol handling is
splitted into SF and HW parts, and actually until negotiation is
completed those parts are completely unrelated to each other, so
requested TCP connection can leak into main stack and main stack can
send some packets which can be considered as MPA negotiation.

> Steve.

Evgeniy Polyakov
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-12-05 17:07    [W:0.060 / U:8.376 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site