From: "Chris Friesen" <cfriesen@nortel.com>
To: Steve French <smfrench@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-cifs-client@lists.samba.org
Subject: Re: SMB2 file system - should it be a distinct module
Date: Mon, 30 Apr 2007 17:15:46 -0600 [thread overview]
Message-ID: <463678A2.7060000@nortel.com> (raw)
In-Reply-To: <524f69650704301552j13cd46e5y53a233af753e0548@mail.gmail.com>
Steve French wrote:
> ...we need to decide whether the kernel
> implementation of SMB2 client should be a distinct module or just part
> of the cifs.ko module.
<snip>
> My guess is that less than 1/3 of the cifs module would overlap - but
> that overlap is enough that it would be easier to do smb2 as part of
> cifs (although it would make the cifs module somewhat larger).
What about pulling out the common code into a helper module, which can
then be used by both cifs and smb2?
Chris
next prev parent reply other threads:[~2007-04-30 23:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 22:52 SMB2 file system - should it be a distinct module Steve French
2007-04-30 23:15 ` Chris Friesen [this message]
2007-05-01 9:06 ` Christoph Hellwig
2007-05-03 13:21 ` [linux-cifs-client] " simo
2007-05-03 14:17 ` Christoph Hellwig
2007-05-03 14:36 ` simo
2007-05-03 14:43 ` Christoph Hellwig
2007-05-03 14:53 ` simo
2007-05-03 15:14 ` Chuck Ebbert
2007-05-03 14:46 ` Gerald Carter
2007-05-03 14:56 ` simo
2007-05-03 15:35 ` Steve French
2007-05-03 15:44 ` Christoph Hellwig
2007-05-04 17:12 ` Jeremy Allison
2007-05-04 17:43 ` simo
2007-05-05 9:55 ` Christoph Hellwig
2007-05-04 18:35 ` Steve French
2007-05-01 9:30 ` Jan Engelhardt
2007-05-01 19:26 ` [linux-cifs-client] Re: SMB2 file system - should it be a distinctmodule Wagner, Chris (GEAE, CBTS)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=463678A2.7060000@nortel.com \
--to=cfriesen@nortel.com \
--cc=linux-cifs-client@lists.samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=smfrench@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox