[email protected] wrote on 06/18/2011 07:56:24 PM:
> On Thu, Jun 16, 2011 at 2:42 PM, Bernard Metzler <[email protected]> wrote: > > --- > > Documentation/networking/siw.txt | 156 > ++++++++++++++++++++++++++++++++++++++ > > 1 files changed, 156 insertions(+), 0 deletions(-) > > create mode 100644 Documentation/networking/siw.txt > > > > diff --git a/Documentation/networking/siw.txt > b/Documentation/networking/siw.txt > > new file mode 100644 > > index 0000000..805e21b > > --- /dev/null > > +++ b/Documentation/networking/siw.txt > > @@ -0,0 +1,156 @@ > > +SoftiWARP: Software iWARP kernel driver module. > > + > > +General > > +------- > > +SoftiWARP (siw) implements the iWARP protocol suite (MPA/DDP/RDMAP, > > +IETF-RFC 5044/5041/5040) completely in software as a Linux kernel module. > > +siw runs on top of TCP kernel sockets and exports the Linux kernel ibverbs > > +RDMA interface. siw interfaces with the iwcm connection manager. > > + > > + > > +Transmit Path > > +------------- > > +If a send queue (SQ) work queue element gets posted, siw tries to send > > +it directly out of the application context. If the SQ was non-empty, > > +SQ processing is done asynchronously by a kernel worker thread. This > > +thread gets scheduled if the TCP socket signals new write space to > > +be available. If during send operation the socket send space becomes > > +exhausted, SQ processing is abandoned until new socket write space > > +becomes available. > > It seems like some information is missing in the above: > - That the siw kernel module creates an iWARP device for each Ethernet > interface found but not for other network interfaces that support the > family of IP protocols. thats correct. thanks. > - Whether or not such an iWARP device is created for Ethernet > interfaces instantiated after the siw kernel module has been loaded. Right. And ... I should probably go for a more dynamic device management, which allows to attach to interfaces instantiated later. Bernard. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
