I agree in theory, but in practice the problem is the
connection setup. On IrDA, you need "someone" to perform the IAS query
on the right device with the right service name (if you are BlueTooth
oriented, think Inquiry + SDP query). If you look IrNET, the actual
data path is only 10% (or less) of the code, most of the code deal
with discovery and connection setup, and this is purely specific to
the PPP over IrDA solution.
By the way, the virtual TTY is not that complex, it's more
complex in the case of IrNET because I actually use the TTY interface
for the control channel. If you remove the control channel, it's
pretty straightforward.
> What do you exactly mean with "kernel space wrapper"?
Like IrNET. There may be way to hook on top of the socket API
from kernel space without modifications (by implementing the bottom
half of the socket layer).
> I guess "user space
> wrapper" is something like VTun (which I tried, and it works like a dream.
> Only, isn't it a bit inefficient to go through user space?)
Did you measure those inefficiencies in practice ?
Jean
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/