On Thu, 14 Jan 2010 15:50:29 -0800 Greg KH <greg@xxxxxxxxx> wrote: > > I'm mostly worried about speed. I just want to be able to dump > > data as quickly as possible. > The serial one should allow you to hit the maximum line-speed for your > hardware, with no overhead for any extra protocols. So I would > recommend using that one. I don't believe it to be feasible to push 4.8 gigabits/s worth of data through the goddamn flip buffers and workqueues. NO WAI. Ethernet is the fastest among networks, at least it has a sane skb infrastructure in the receive path. Remember that Ethernet can deliver jumbo packets (although I don't know if CDE-Ether allows them). The fastest of them all is, IMHO, storage. It has s/g and long I/Os. It is zero-copy on read. Unfortunately the storage API model is not suited for endless streams. So if I really needed to push the limits, I would go custom by setting up large shared buffers (e.g. either mmap() or getuserpages) and doing zero-copy there. If I cared about interoperability and/or not being a jerk to whoever needs to maintain the code after I'm gone, then Ethernet. But serial on the input path? That's just wrong. -- Pete -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
