From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Gunthorpe Subject: Re: [PATCH v2] allow passthrough of rmpp packets to user mad clients Date: Fri, 18 Jun 2010 10:38:42 -0600 Message-ID: <20100618163842.GJ4630@obsidianresearch.com> References: <4C2744E8AD2982428C5BFE523DF8CDCB49A488DAD8@MNEXMB1.qlogic.org> <4C2744E8AD2982428C5BFE523DF8CDCB49D09E7C2F@MNEXMB1.qlogic.org> <20100618154134.GA12884@obsidianresearch.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: "Hefty, Sean" Cc: Mike Heinz , Roland Dreier , "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Hal Rosenstock List-Id: linux-rdma@vger.kernel.org On Fri, Jun 18, 2010 at 09:33:01AM -0700, Hefty, Sean wrote: > > Why not just add byte-stream like APIs to the kernel interface for > > RMPP? > > RMPP is more like IP segmentation than TCP segmentation. Why do you say that? Each RMPP session is identified by a unique, ID, can run transfer data in both directions, does reassembly, re-ordering, re-transmit, and can transfer unbounded amounts of data, without knowing how much in advance. Sounds exactly like TCP to me.. Jason -- 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