lkml.org 
[lkml]   [2006]   [Mar]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: eCryptfs Design Document
From
Date
> > > One dutifully wonders whether all this functionality could be
> > > provided via FUSE...
> >
> > My main concern with FUSE has to do with shared memory mappings.
>
> OK. But I'm sure Miklos would appreciate help with that ;)

You bet.

> > My next concern is with regard to performance impact of constant
> > context switching during page reads and writes.
>
> Maybe. One could estimate the cost of that by benchmarking an existing
> (efficient) FUSE fs and then add fiddle factors. If the number of copies
> is the same for in-kernel versus FUSE then one would expect the performance
> to be similar. Especially if the encrypt/decryption cost perponderates.

The main overhead of FUSE is not in copies, but in context switching.
For I/O that can be mitigated by doing it in big chunks, otherwise the
only solution is adding more processors.

Miklos
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-03-25 08:42    [W:0.061 / U:0.328 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site