[16781] in Kerberos_V5_Development
Re: Kernel subset design issues
daemon@ATHENA.MIT.EDU (Simo Sorce)
Tue Apr 26 09:41:56 2011
From: Simo Sorce <ssorce@redhat.com>
To: Sam Hartman <hartmans@mit.edu>
In-Reply-To: <tslboztqvg5.fsf@mit.edu>
Date: Tue, 26 Apr 2011 09:41:49 -0400
Message-ID: <1303825309.23464.36.camel@willson.li.ssimo.org>
Mime-Version: 1.0
Cc: krbdev@mit.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
On Tue, 2011-04-26 at 04:16 -0400, Sam Hartman wrote:
> Does anyone plan to do a kernel CIFS implementation or a kernel
> implementation requiring parts of DCE RPC?
Afaik Solaris has a kernel CIFS *server* implementation.
This will probbaly require DCE RPC.
Linux has a CIFS *client* implementation.
This doesn;t so far, but might at some point.
> If so, the IOV routines will be needed.
> Also, if your kernel can support it, it seems like doing in-place crypto
> would be a real win, and thus IOV would be desirable.
Yes, this is true.
> Why not only use IOV and enable the #define to do everything in terms of
> iov instead of having iov and non-iov wrap implementations?
Sounds like a good idea to me.
Simo.
--
Simo Sorce * Red Hat, Inc * New York
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
