From: Oleg Drokin <green@namesys.com>
To: Manuel Krause <manuel.krause@mb.tu-ilmenau.de>
Cc: reiserfs-list <reiserfs-list@namesys.com>
Subject: Re: Copy time comparison 2.4.20-pre6 <-> 2.4.19+data-logging (was:Compatibility of current 2.4.19.pending ...)
Date: Fri, 13 Sep 2002 11:37:35 +0400 [thread overview]
Message-ID: <20020913113735.A6022@namesys.com> (raw)
In-Reply-To: <3D81076E.6090408@mb.tu-ilmenau.de>
Hello!
On Thu, Sep 12, 2002 at 11:30:22PM +0200, Manuel Krause wrote:
> >When I see the discussion about the new block-allocator, the testing
> >directory etc. I assume a definite "No." (Please, please, correct me, if
> ;-) You really didn't correct me so far. Mmh. :-(
Datalogging is incompatible with stuff in testing directory. It won't apply
cleanly to new block allocatior, but that's can be easily fixed.
> >So, for the overnight change to pre-kernel 7, where are the new
> >data-logging patches Hans even announced to lkml?
> So I really got a 2.4.20-pre6 compiled with the
> preempt-kernel-rml-2.4.20-pre5-1.patch and Olegs fix he sent to the list
> yesterday. BTW, have the testing patches from -pre5 gone into -pre6? It
> isn't clear to me.
Testing patches were merged into -pre6 by Marcelo's mistake and -pre7
have these patches removed already.
> Application startup timings of NS-7.0 and OOo-1.0.1 didn't increase. :-))
Sure, read code path did not changed at all.
> I hope I don't need to comment on the values...
Sure. datalogging and new file_write code are not solutions to same problem.
These are solutions for different problems and can be used together (after
merging of course) for even better performance, I hope ;)
Bye,
Oleg
next prev parent reply other threads:[~2002-09-13 7:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-12 0:24 Compatibility of current 2.4.19.pending patchset with old data-logging?? Manuel Krause
2002-09-12 13:28 ` newbie how to darren
2002-09-12 14:37 ` Hans Reiser
2002-09-12 15:12 ` Guillermo Torreiro
2002-09-12 21:30 ` Copy time comparison 2.4.20-pre6 <-> 2.4.19+data-logging (was:Compatibility of current 2.4.19.pending ...) Manuel Krause
2002-09-13 7:37 ` Oleg Drokin [this message]
2002-09-13 23:07 ` Manuel Krause
2002-09-14 9:02 ` Oleg Drokin
2002-09-17 0:53 ` Manuel Krause
[not found] ` <3D867C14.5060404@mb.tu-ilmenau.de>
2002-09-17 6:33 ` Oleg Drokin
2002-09-17 13:56 ` Manuel Krause
2002-09-17 14:00 ` Oleg Drokin
2002-09-17 17:39 ` Manuel Krause
2002-09-18 5:20 ` Oleg Drokin
2002-09-19 1:14 ` Manuel Krause
2002-09-19 6:34 ` Oleg Drokin
2002-09-19 15:52 ` Manuel Krause
2002-09-19 16:01 ` Oleg Drokin
2002-09-23 0:36 ` Manuel Krause
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=20020913113735.A6022@namesys.com \
--to=green@namesys.com \
--cc=manuel.krause@mb.tu-ilmenau.de \
--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.