michael chang schrieb:
On 9/20/05, Gregory Maxwell [EMAIL PROTECTED] wrote:
An interesting idea: select the algo and a range of compression
levels per file, but select the actual compression level at flush time
based on some estimate of how loaded the system is.. :)
Probably not worth it even
On Sep 20, 2005, Stephen Pollei [EMAIL PROTECTED] wrote:
it takes gcc -Wall test_proto.c --std=c99 -pedantic-errors to cause it
not to create the a.out .
So gcc should have caused an error as I didn't set --std=gnu99 .. bad
compiler.
So I don't know howto get gcc to follow the standards in
An interesting idea: select the algo and a range of compression
levels per file,
A simple check on wether it's an already compressed file (using file
extension and magic number) should be quite easy to do and cheap.
Now, intrigued by this lzo thingie, I ran a little benchmark on my
Pysiak Satriani wrote:
Hi,
recent threads on compression made me think about the algorithms.
Will there be just one compression algorithm for everything,
or many and ways to choose from them?
Will it be possible to, say, write plugins of your own to do
the compression?
Hello.
Reiser4
Hello.
Среда 21 сентября 2005 02:10 | Pavel Machek:
At tytso's request... could you put some reiser3 and reiser4
filesystem images inside test data?
I've not tested Reiser3, but Reiser4 images (fsck.okay and repaired
fsck.damaged is here (sorry, I have no log of 125 passes test run, only
one
On Wednesday 21 September 2005 01:11, Theodore Ts'o wrote:
On Tue, Sep 20, 2005 at 12:18:46PM -0600, Jonathan Briggs wrote:
I use Reiser3 and Reiser4 on all my systems and fsck has always worked
even if it has been much slower than I would like. The only problems
I've experienced have
On Wednesday 21 September 2005 07:05, Hans Reiser wrote:
Ric Wheeler wrote:
Hans Reiser wrote:
Ric Wheeler wrote:
As an earlier thread on lkml showed this summer, we still have a long
way to go to getting consistent error semantics in face of media
failures between the various
Hans Reiser writes:
Stephen Pollei wrote:
Also note my opinion, doesn't really count if you grep the kernel
sources for pollei, you won't find anything.
Your opinion counts, but lets see what Nikita says before I say
anything. Nikita is more expert than I in regards
Gregory Maxwell wrote:
On 9/20/05, Hans Reiser [EMAIL PROTECTED] wrote:
Another goal of the group should be to formulate a requested set of
changes or extensions to the makers of drives and other storage
systems. For example, it might be advantageous to be able to disable
bad block
Gregory Maxwell wrote:
On 9/20/05, David Masover [EMAIL PROTECTED] wrote:
Probably lzo, which is already used for other things like network
connections (ssh, openvpn, and so on). The nice thing about lzo is that
it's fast, faster than gzip or bzip2, and gets decent compression -- not
Edward Shishkin [EMAIL PROTECTED] wrote:
David, would you please review the following:
KEY MANAGEMENT IN REISER4
There's a mailing list for such discussions:
[EMAIL PROTECTED]
I should update the MAINTAINERS file to reflect this.
Reiser4 will register its own
PFC wrote:
An interesting idea: select the algo and a range of compression
levels per file,
A simple check on wether it's an already compressed file (using
file extension and magic number) should be quite easy to do and cheap.
Now, intrigued by this lzo thingie, I ran a little
Nikita Danilov wrote:
Hans Reiser writes:
Stephen Pollei wrote:
Also note my opinion, doesn't really count if you grep the kernel
sources for pollei, you won't find anything.
Your opinion counts, but lets see what Nikita says before I say
anything. Nikita is more
Ric Wheeler wrote:
Gregory Maxwell wrote:
On 9/20/05, Hans Reiser [EMAIL PROTECTED] wrote:
Another goal of the group should be to formulate a requested set of
changes or extensions to the makers of drives and other storage
systems. For example, it might be advantageous to be able to
Hans Reiser wrote:
Ric Wheeler wrote:
Gregory Maxwell wrote:
On 9/20/05, Hans Reiser [EMAIL PROTECTED] wrote:
Another goal of the group should be to formulate a requested set of
changes or extensions to the makers of drives and other storage
systems. For example, it might be
Hans Reiser writes:
[...]
So what do you suggest we change it to, Nikita?
Just remove #ifdef/#endif as was suggested.
Nikita.
Hans Reiser [EMAIL PROTECTED] wrote:
At the this time we have no idea which patch is responsible, probably in
a day or two we'll have a patch to fix it.
OK. I assume this performance change is demonstrable in just
2.6.14-rc2+reiser4? Beware that there are other changes in the -mm lineup
Nikita Danilov wrote:
Hans Reiser writes:
Horst von Brand wrote:
Funny that the texbook algorithms aren't used in real life. Wonder why...
Try BSD. If the BSD book can be believed, they usetexbook algorithms.
The textbook one-way elevator (as indeed exemplified by
Nikita Danilov wrote:
Hans Reiser writes:
[...]
Yes, and one can compensate for them fairly cleanly. I can't say more
without the customer releasing the code first.
That's the point: text-book algorithms are usually useless as is. They
need adjustments and changes to work in real
Theodore Ts'o wrote:
On Tue, Sep 20, 2005 at 09:41:36AM -0500, David Masover wrote:
And personally, if it was my FS, I'd stop working on fsck after it was
able to check. That's what it's for. To fix an FS, you wipe it and
restore from backups.
If that's Reiser4's philosophy, just
Hello,
as YaST and fdisk showed different output for the partions of my
hard-disk, I got confused and lost the correct start point for my
partition /dev/hda5.
Recreation of superblocks by reiserfsck --rebuild-sb creates a
superblock, but afterwards, --rebuild-tree terminates with a message
that
Important update regarding your business
for Sept 2005.
===Please read:
We have emailed you before regarding your
business and how we can boost your paid
members right away.
Just a quick insight from us to let you know
that each week, right now, our client's that
are in business with a program
22 matches
Mail list logo
