All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Christian Mayrhuber <christian.mayrhuber@gmx.net>
Cc: reiserfs-list@namesys.com
Subject: Re: [patch] Repacker stats
Date: Sat, 23 Oct 2004 09:25:49 -0700	[thread overview]
Message-ID: <417A860D.9010701@namesys.com> (raw)
In-Reply-To: <200410231033.29164.christian.mayrhuber@gmx.net>

Christian Mayrhuber wrote:

>On Friday 22 October 2004 19:38, Spam wrote:
>  
>
>>  Hello,
>>
>>  I was interested in testing the repacker statistics tool that Piotr
>>  Neuman wrote (and others later added to). But from what I can see
>>  the repacker is disabled in 2.6.9-rc4-mm1, because of this patch:
>>
>>     
>>    
>>
>http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.9-rc4/2.6.9-rc4-mm1/broken-out/reiser4-disable-repacker.patch
>  
>
>>  Is there something wrong with the repacker that is has to be
>>  disabled?
>>
>>  ~S
>>  
>>    
>>
>>>Hi
>>>      
>>>
>>>This is my second attempt at repacker statistics, this time based on 
>>>      
>>>
>comments
>  
>
>>>from Alex Zarochentsev (thanks ;-).
>>>      
>>>
>>>This patch allows reading of repacker stats while it is working. It 
>>>      
>>>
>creates
>  
>
>>>two files in repacker sysfs hierarchy: formatted_nodes and 
>>>      
>>>
>unformatted_nodes,
>  
>
>>>which correspond to the stats that repacker prints after it has finished.
>>>      
>>>
>>>Download:
>>>      
>>>
>>>http://kem.p.lodz.pl/~peter/reiser4_repacker_stats-2.patch
>>>      
>>>
>>>Regards
>>>      
>>>
>>>Piotr Neuman
>>>      
>>>
>>´
>>
>>-- 
>>
>>    
>>
>
>Currently the repacker is known to corrupt the filesystem, that's
>why it's disabled, I guess.
>
>  
>
There are two reasons:

1) functionality that is not stable should be turned off until it is 
stable ("...." and repacker both).

2) we aren't making payroll and need something nonessential to bundle 
with support if we want people to buy support so that I am to be able to 
quit my day job and pay people.  There is nothing less essential yet 
still salable than a repacker/resizer.  ext3 had a proprietary resizer, 
so it is not an innovation by us.

reiser4 development is going at greatly reduced speed due to our needing 
to take contracts involving other kernel work rather than working on 
reiser4.  I am basically unable to spend time reviewing reiser4 code 
because I have this day job fixing things not related to reiser4 in the 
kernel.  I am glad to have the day job, but getting money from our work 
on reiser4 would be better.....

I have also asked both the EU and the US for money, wish me luck.  I'd 
like to start working on the enhanced semantics for ReiserFS, but I need 
money to do that.  We are losing momentum vs. Apple and MS.  The resizer 
might bring in the money for enhanced semantics work.

  reply	other threads:[~2004-10-23 16:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-20 19:59 [patch] Repacker stats Piotr Neuman
2004-10-22 17:38 ` Spam
2004-10-23  8:33   ` Christian Mayrhuber
2004-10-23 16:25     ` Hans Reiser [this message]
2004-10-24 12:52       ` Spam
  -- strict thread matches above, loose matches on Subject: below --
2004-10-17  8:01 Piotr Neuman
2004-10-17 14:25 ` mjt

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=417A860D.9010701@namesys.com \
    --to=reiser@namesys.com \
    --cc=christian.mayrhuber@gmx.net \
    --cc=reiserfs-list@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.