Clemens Eisserer wrote:
>Hi again,
>
>Wow does that mean cryptocompress is almost ready for primetime (next
>months or so)?!
>I've been waiting for something like this for ages, it would be so
>great if that could turn into reality soon.
>
>I am quite enthusiastic how it will perform on the Dual-A
Hi again,
Wow does that mean cryptocompress is almost ready for primetime (next
months or so)?!
I've been waiting for something like this for ages, it would be so
great if that could turn into reality soon.
I am quite enthusiastic how it will perform on the Dual-Athlon64 + 4x
Software-Raid-5 (PAT
Hi,
Am Donnerstag, den 26.01.2006, 21:41 +0300 schrieb Edward Shishkin:
> Danny Milosavljevic wrote:
>
> >Hi,
> >
> >Nice :)
> >
> >Just curious, is there a description how to enable cryptcompress for
> >files somewhere? (or is it still bleeding-edge ? :))
> >
> >cheers,
> > Danny
> >
> >
>
>
Hello,
On Thursday 26 January 2006 21:56, Jens Axboe wrote:
> On Thu, Jan 26 2006, Edward Shishkin wrote:
> > Jens Axboe wrote:
> > >On Wed, Jan 25 2006, Hans Reiser wrote:
> > >>Notice how CPU speed (and number of cpus) completely determines
> > >>compression performance.
> > >>
> > >>cryptcompre
Jens Axboe wrote:
>
>Yeah and that's ok, I was just interested in seeing some more
>interesting compression benchmarks so I wondered if you had done that.
>
>
>
I think "random minor benchmark" was an apt description, yes.;-)
First we will debug it fully. Then we will figure out how to change
m
On Fri, Jan 27 2006, Hans Reiser wrote:
> Jens Axboe wrote:
>
> > So the systime quoted above is basically useless, it doesn't reflect the
> >
> >real time spent in the kernel by far. I think you should note that when
> >you post these scores, otherwise you're really showing a skewed picture.
> >
Jens Axboe wrote:
> So the systime quoted above is basically useless, it doesn't reflect the
>
>real time spent in the kernel by far. I think you should note that when
>you post these scores, otherwise you're really showing a skewed picture.
>
>
>
He wasn't expecting me to post the benchmark, an
On Thu, Jan 26 2006, Hans Reiser wrote:
> Edward Shishkin wrote:
>
> >
> > I guess this is because real compression is going in background
> > flush, not in sys_write->write_cryptcompress (which just copies
> > user's data to page cache). So in this case we have something
> > very similar to ext2.
On Thu, Jan 26 2006, Edward Shishkin wrote:
> Jens Axboe wrote:
>
> >On Thu, Jan 26 2006, Edward Shishkin wrote:
> >
> >
> >>Jens Axboe wrote:
> >>
> >>
> >>
> >>>On Wed, Jan 25 2006, Hans Reiser wrote:
> >>>
> >>>
> >>>
> >>>
> Notice how CPU speed (and number of cpus) completely det
Edward Shishkin wrote:
>
> I guess this is because real compression is going in background
> flush, not in sys_write->write_cryptcompress (which just copies
> user's data to page cache). So in this case we have something
> very similar to ext2. Reiser4 plain write (write_unix_file) is
> more compl
Jens Axboe wrote:
>On Wed, Jan 25 2006, Hans Reiser wrote:
>
>
>>Notice how CPU speed (and number of cpus) completely determines
>>compression performance.
>>
>>cryptcompress refers to the reiser4 compression plugin, (unix file)
>>refers to the reiser4 non-compressing plugin.
>>
>>Edward Shishki
Jens Axboe wrote:
On Thu, Jan 26 2006, Edward Shishkin wrote:
Jens Axboe wrote:
On Wed, Jan 25 2006, Hans Reiser wrote:
Notice how CPU speed (and number of cpus) completely determines
compression performance.
cryptcompress refers to the reiser4 compression plugin, (unix fil
On Thu, Jan 26 2006, Edward Shishkin wrote:
> Jens Axboe wrote:
>
> >On Wed, Jan 25 2006, Hans Reiser wrote:
> >
> >
> >>Notice how CPU speed (and number of cpus) completely determines
> >>compression performance.
> >>
> >>cryptcompress refers to the reiser4 compression plugin, (unix file)
> >>re
Danny Milosavljevic wrote:
Hi,
Nice :)
Just curious, is there a description how to enable cryptcompress for
files somewhere? (or is it still bleeding-edge ? :))
cheers,
Danny
Hello.
If you have a free partition and a time to report about
possible bugs, we'll send you a setup against 2.6
Jens Axboe wrote:
On Wed, Jan 25 2006, Hans Reiser wrote:
Notice how CPU speed (and number of cpus) completely determines
compression performance.
cryptcompress refers to the reiser4 compression plugin, (unix file)
refers to the reiser4 non-compressing plugin.
Edward Shishkin wrote:
Hi,
Nice :)
Just curious, is there a description how to enable cryptcompress for
files somewhere? (or is it still bleeding-edge ? :))
cheers,
Danny
On Wed, Jan 25 2006, Hans Reiser wrote:
> Notice how CPU speed (and number of cpus) completely determines
> compression performance.
>
> cryptcompress refers to the reiser4 compression plugin, (unix file)
> refers to the reiser4 non-compressing plugin.
>
> Edward Shishkin wrote:
>
> > Here are t
Notice how CPU speed (and number of cpus) completely determines
compression performance.
cryptcompress refers to the reiser4 compression plugin, (unix file)
refers to the reiser4 non-compressing plugin.
Edward Shishkin wrote:
> Here are the tests that vs asked for:
> Creation (dd) of 20 tarfiles
18 matches
Mail list logo
