All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manuel Krause <manuel.krause@mb.tu-ilmenau.de>
To: Chris Mason <mason@suse.com>
Cc: reiserfs-list <reiserfs-list@namesys.com>
Subject: Re: [PATCH CFT] tons of logging patches
Date: Wed, 05 Jun 2002 23:27:16 +0200	[thread overview]
Message-ID: <3CFE8234.7010006@mb.tu-ilmenau.de> (raw)
In-Reply-To: 3CFE7EFB.6080203@mb.tu-ilmenau.de

On 06/05/2002 11:13 PM, Manuel Krause wrote:
> On 06/04/2002 03:12 PM, Chris Mason wrote:
>  > On Mon, 2002-06-03 at 23:28, Manuel Krause wrote:
>  >
>  >
>  >>So, VMware is stable with it, too, on my well known "heavy-private-test"
>  >>of it (running Norton SpeedDisk at least twice within a most recent
>  >>VMware Win98). It doesn't show greatly different timings than to my
>  >>setup before though having a different disk i/o pattern (due to the
>  >>missing aa patches)... and me having a reduced RAM from 512to256MB at
>  >>the moment. And I should be honest to say I can't give exact timings as
>  >>the important disk contents changed during last weeks. But the
>  >>disk-access-times/related-to-the-content are definitively _not_ higher
>  >>than before!
>  >
>  >
>  > same speed on 1/2 the ram isn't bad ;-)
>  >
> [...]
> Don't know where to reply best...
[...]

BTW, what is this "only" diff good for (is it worth to recompile, I mean):
# diff '03-beta-data-logging-6.diff' '03-beta-data-logging-5.diff'
2777c2777
< +  if (SB_JOURNAL(p_s_sb)->j_num_lists > 512) {
---
 > +  if (SB_JOURNAL(p_s_sb)->j_num_lists > 256) {

Thank you,

Manuel

> 
> I was extraordinary glad to see the explicit wording of the mounted 
> partition in the logs we missed for so long time!
> 
> Thanks for your help,
> 
> Manuel
> 




  reply	other threads:[~2002-06-05 21:27 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-03  3:51 [PATCH CFT] tons of logging patches Chris Mason
2002-06-03  4:04 ` Chris Mason
2002-06-03  8:46 ` Matthias Andree
2002-06-03 12:26   ` Chris Mason
2002-06-04  0:45 ` Manuel Krause
2002-06-04  1:49 ` Manuel Krause
2002-06-04  2:20   ` Chris Mason
2002-06-04  3:28     ` Manuel Krause
2002-06-04 13:12       ` Chris Mason
2002-06-05 21:13         ` Manuel Krause
2002-06-05 21:27           ` Manuel Krause [this message]
2002-06-05 21:32             ` Chris Mason
2002-06-06  0:09             ` Chris Mason
2002-06-06  4:59               ` Manuel Krause
2002-06-12 22:32               ` Manuel Krause
2002-06-17  0:47                 ` Chris Mason
2002-06-17  0:31                   ` Manuel Krause
2002-06-17 19:04                     ` Chris Mason
2002-06-21  0:25                       ` Chris Mason
2002-06-25  0:55                         ` Manuel Krause
2002-06-28 13:51                       ` Chris Mason
2002-07-02 18:16                         ` Chris Mason
2002-07-03 20:56                           ` Chris Mason
2002-07-04  0:28                             ` Manuel Krause
2002-07-08 13:51                               ` Chris Mason
2002-07-09  0:22                                 ` [PATCH CFT] tons of logging patches + addon Manuel Krause
2002-06-04  2:57   ` [PATCH CFT] tons of logging patches Chris Mason
2002-06-04  4:16     ` Manuel Krause
2002-06-04 13:34       ` Chris Mason
2002-06-04 21:20         ` Hans Reiser
2002-06-05  0:16           ` Robert Brockway
2002-06-05  8:43           ` Oleg Drokin
  -- strict thread matches above, loose matches on Subject: below --
2002-06-04 15:48 berthiaume_wayne
2002-06-04 16:55 ` Chris Mason
2002-06-22 20:02 Dieter Nützel
2002-06-24 19:05 ` Chris Mason
2002-07-09 13:52   ` Dieter Nützel
2002-07-09 14:00     ` Chris Mason
2002-07-14  0:52 Manuel Krause
2002-08-02 12:28 ` Chris Mason

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=3CFE8234.7010006@mb.tu-ilmenau.de \
    --to=manuel.krause@mb.tu-ilmenau.de \
    --cc=mason@suse.com \
    --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.