On Fri, Apr 22, 2011 at 02:33:08PM +0400, Pavel Shilovsky wrote: > I've just thought about to share tcp_server_info struct between > different protocol connections. So, we can use cifs and smb2 > connection on the same server and don't keep two socket connections. > What do you think about to store protocol_id in ses_info rather that > tcp_server_info? What about prototyping it either first, and then review an actually complete smb2 implementation on a branch / as a patchkit do decide what makes most sense? -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
