From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Shilovsky Subject: Re: mids and cifs sendrcv2 Date: Tue, 26 Apr 2011 23:40:41 +0400 Message-ID: References: <20110422114526.GA31546@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Cc: Steve French , linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-fsdevel To: Christoph Hellwig Return-path: In-Reply-To: <20110422114526.GA31546-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org> Sender: linux-cifs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-fsdevel.vger.kernel.org 2011/4/22 Christoph Hellwig : > 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? Yes, you are right. I am going to create such a branch and start to merge smb2 code there. -- Best regards, Pavel Shilovsky.