All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
To: Rob Mueller <robm@fastmail.fm>, Chris Mason <mason@suse.com>
Cc: ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: 2.4.22pre7aa1 ;-) Mit O(1) aber leider kein pre-emption
Date: Tue, 22 Jul 2003 13:54:23 +0200	[thread overview]
Message-ID: <200307221354.23397.Dieter.Nuetzel@hamburg.de> (raw)
In-Reply-To: <001c01c35012$abcc9250$2b8bddcb@lifebook>

Am Dienstag, 22. Juli 2003 07:32 schrieb Rob Mueller:
> > Data-logging in the works?
>
> I've managed to get this working. Patched to 2.4.22-pre7-aa and then
> applied the data logging patches for 2.4.22-pre5 (see
> ftp://ftp.suse.com/pub/people/mason/patches/data-logging/2.4.22) which
> seems to work fine. I saw two problems though, a function (can't remember
> which one) was duplicate defined in mm/filemap.c (exactly the same code
> appeared twice), and an EXPORT_SYMBOL() from mm/filemap.c had to be removed
> as well.

As always...;-)

> However removing them seemed to work fine.

I hoped that, but there is sadly no simple pre-emption patch for -aa.
With pre-emption I have much _more_ (IO-) throughput.

> The patches I applied:
>
> 04-reiserfs-sync_fs-4.diff
> 05-data-logging-39.diff
> 06-logging-export.diff
> 06-reiserfs-jh-3.diff
> 06-write_times.diff

Isn't needed 'cause it is in -aa.

> search_reada-5.diff

Thanks,
	Dieter


      reply	other threads:[~2003-07-22 11:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-21 14:39 2.4.22pre7aa1 ;-) Mit O(1) aber leider kein pre-emption Dieter Nützel
2003-07-21 15:38 ` Manuel Krause
2003-07-21 15:55   ` Manuel Krause
2003-07-30  5:11     ` Manuel Krause
2003-07-22  5:32 ` Rob Mueller
2003-07-22 11:54   ` Dieter Nützel [this message]

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=200307221354.23397.Dieter.Nuetzel@hamburg.de \
    --to=dieter.nuetzel@hamburg.de \
    --cc=mason@suse.com \
    --cc=reiserfs-list@namesys.com \
    --cc=robm@fastmail.fm \
    /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.