All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manuel Krause <manuelkrause@netscape.net>
To: "Yury Yu. Rupasov" <yura@yura.polnet.botik.ru>
Cc: reiserfs-list <reiserfs-list@namesys.com>
Subject: Re: BTW: 2.4.19-patches-to-come?
Date: Tue, 07 May 2002 22:41:58 +0200	[thread overview]
Message-ID: <3CD83C16.2040902@netscape.net> (raw)
In-Reply-To: 3CD7DC32.1D138A59@yura.polnet.botik.ru

Hi!

On 05/07/2002 03:52 PM, Yury Yu. Rupasov wrote:

> Manuel Krause wrote:
> 
>>Hi!
>>
[...]
>>
>>4.) a hint why there is iicache code in the latest
>>     speedup-compound-patch (so that the latest iicache patch
>>     would not apply)
>>
> 
> The iicache patch is inside compound-speedup-2.patch already.
> So, you can use just compound-speedup-2.
> 
>>Best regards for your stable ReiserFS, at all,
>>
>>even under "settings" with 2.4.19-pre7 +reiserfs.pending +latest
>>reiserfs.compound-speedup +aa.vm-for-2.4.19-pre7 +akpm.read-latency-2
>>+rml.preempt-kernel + rml.lock-break +some-more nice aa.patches...
>>That's a valuably fast & interactive experience!
>>
>>Manuel
>>
> 
> Thank you Manuel for testing,
> Yura.
> 


O.k. I just assumed that (iicache=in) was true since reading and 
applying the patch and _then_ this "compound" is much more stable than 
the previous versions of iicache. I.e. it does not corrupt my Netscape6 
and KDE files-in-use any more. And it really does not show slowdowns in 
applications load times at all. Maybe Dieter could report the same.

I can't say if it is faster or slower as I revised my systems' chipset 
and bus settings (hdparm, lilo->kernel and powertweak) during the last 
weeks to have an overally more common and stable setup.

Thanks for providing a usable and  applyable patch on Namesys ftp, Yura,

Manuel




  reply	other threads:[~2002-05-07 20:41 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-07  1:15 BTW: 2.4.19-patches-to-come? Manuel Krause
2002-05-07  5:22 ` Oleg Drokin
2002-05-07 14:02   ` Yury Yu. Rupasov
2002-05-07 19:35   ` Manuel Krause
2002-05-08  5:30     ` Oleg Drokin
2002-05-08 13:04       ` Chris Mason
2002-05-08 13:08         ` Oleg Drokin
2002-05-08 13:16           ` Chris Mason
2002-05-08 13:20             ` Oleg Drokin
2002-05-08 13:34     ` Chris Mason
2002-05-17  1:49       ` Manuel Krause
2002-05-17  4:56         ` Oleg Drokin
2002-05-17  9:47           ` Pierre Etchemaite
2002-05-17  9:47             ` Oleg Drokin
2002-05-07 13:52 ` Yury Yu. Rupasov
2002-05-07 20:41   ` Manuel Krause [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-17 15:36 Dieter Nützel
2002-05-17 15:47 ` Chris Mason
2002-05-17 18:20   ` Dieter Nützel
2002-05-17 18:26     ` Dieter Nützel
2002-05-17 15:54 ` Oleg Drokin
2002-05-17 17:05   ` Dieter Nützel
2002-05-17 18:28     ` Oleg Drokin
2002-05-17 19:44       ` Dieter Nützel
2002-05-18  5:44         ` Oleg Drokin
2002-05-18 13:18           ` Dieter Nützel
2002-05-18 16:29             ` Oleg Drokin

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=3CD83C16.2040902@netscape.net \
    --to=manuelkrause@netscape.net \
    --cc=reiserfs-list@namesys.com \
    --cc=yura@yura.polnet.botik.ru \
    /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.