All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Manuel Krause <manuelkrause@netscape.net>
Cc: reiserfs-list <reiserfs-list@namesys.com>
Subject: Re: Data-logging and md as / fs bug
Date: Tue, 13 May 2003 18:59:23 +0400	[thread overview]
Message-ID: <20030513145923.GJ12963@namesys.com> (raw)
In-Reply-To: <3EC10879.1040902@netscape.net>

Hello!

On Tue, May 13, 2003 at 05:00:09PM +0200, Manuel Krause wrote:

> >No. I have old patch instead that applies to 2.4.20 and basically every 
> >other kernel
> >and that I am pushing to Marchelo as this iget5_locked is too intrusive at 
> >current 2.4
> >development stage.
> In what kind? Or: What kind of intrusion do you mean then (see below)?!

It touches too much code, the code vfs code, nfs and coda (and reiserfs of course).

> >This old patch is attached.
> >>Always appreciated are less intrusive ones regarding i/o speed ;-))
> >I/O speed should be the same with all the aproaches.
> >The patch below is a bit more cpu hungry as it introduces one more 
> >spinlock.
> But, errhm, why should I use a patch that uses more cpu and doesn't 
> speed up disk i/o (see above)???

Well, you are free to use that iget5_locked backport, but I cannot feed it to Marcelo now,
and I need the bug to be fixed, so I am sending this old patch now and will revert to
proper fix asfter 2.4.22 is out.
(when it is out, you can revert the patch I sent in previous mail and apply the iget5_locked backport).
And the more testing is better as always ;)

> I only did a very little testing when the discussions on 
> iget5_locked_for-2.4.21-pre5-datalogging.diff, kinoded-? + 
> inode-dirty-for-kinoded began. And it seemed that kinoded + inode-dirty 
> doesn't make a difference without quota (as Chris already pointed out) 
> but that I loose 2s on OpenOffice- and 1s on Netscape7-startup time 
> without your -pre5 patch. Is that possible or should I improve my 
> looking-at-the-clock or re-verify that?

Hm. Loose as in startup now takes XX sec more ? Or XX sec less?

Thank you.

Bye,
    Oleg

  reply	other threads:[~2003-05-13 14:59 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-03  0:07 Data-logging for 2.4.21-rc1+ (again) Manuel Krause
2003-05-03 10:31 ` Oleg Drokin
2003-05-06 19:34   ` Data-logging and md as / fs bug Christian Mayrhuber
2003-05-06 19:44     ` Chris Mason
2003-05-06 19:56       ` Dieter Nützel
2003-05-08 13:31         ` Chris Mason
2003-05-09 20:21           ` Manuel Krause
2003-05-11 12:58             ` Chris Mason
2003-05-12  7:29           ` Oleg Drokin
2003-05-13 14:15             ` Manuel Krause
2003-05-13 14:25               ` Oleg Drokin
2003-05-13 15:00                 ` Manuel Krause
2003-05-13 14:59                   ` Oleg Drokin [this message]
2003-05-13 15:39                     ` Manuel Krause
2003-05-13 15:42                       ` Oleg Drokin
2003-05-15 13:31                         ` Manuel Krause
2003-05-13 21:52               ` Newsmail
2003-05-13 22:18                 ` Christian Mayrhuber
2003-05-14  5:40                 ` Oleg Drokin
2003-05-06 20:53       ` Christian Mayrhuber
2003-05-06 21:22         ` Chris Mason
2003-05-07 12:34         ` Chris Mason
2003-05-07 14:41           ` Christian Mayrhuber
2003-05-07 14:43             ` Chris Mason
2003-05-07 14:52               ` Christian Mayrhuber
2003-05-07 15:23                 ` Chris Mason
2003-05-08 13:35                   ` Chris Mason
2003-05-12  7:37                   ` Oleg Drokin
  -- strict thread matches above, loose matches on Subject: below --
2003-05-09 11:17 Kerin Millar

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=20030513145923.GJ12963@namesys.com \
    --to=green@namesys.com \
    --cc=manuelkrause@netscape.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.