Let's suppose that I'm writing a experimental distributed filesystem that needs to open a TCP socket to another machines on the LAN, keep a pool of connections and be always aware of new data arriving (like a userspace select()). What's the best approach to implement this ? Is it better to keep all the TCP socket stuff in userspace and use an interface like netlink to talk with it ? Or, since we're talking about a filesystem (where performance is a must), is it better to keep it in kernel mode ?
Thanks! -- "Quanto mais conheço os homens, mais gosto dos meus cavalos" - João Figueiredo, former Brazilian president. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
