From: Chris Mason <mason@suse.com>
To: Manuel Krause <manuel.krause@mb.tu-ilmenau.de>
Cc: reiserfs-list <reiserfs-list@namesys.com>
Subject: Re: [PATCH] new data logging and quota patches available
Date: 05 Mar 2003 22:46:13 -0500 [thread overview]
Message-ID: <1046922372.2161.275.camel@tiny.suse.com> (raw)
In-Reply-To: <3E66B73D.6030008@mb.tu-ilmenau.de>
On Wed, 2003-03-05 at 21:49, Manuel Krause wrote:
> On 02/28/2003 02:32 PM, Chris Mason wrote:
> >>>Comparing data-logging-35 vs data-logging-36+kinoded-9+dirty_inode I
> >>>have a performance increase of 2.5% for the new data-logging. Like you
> >>>say above.
> >>
> >>But... though you were right with 2.4.21 data-logging performance
> >>relations: --> What was causing that performance loss between 2.4.19
> >>+data-logging and now???
> >>
> > Did you exclude your changing dataset as a potential cause? If not I'm
> > very interested in the details.
>
> Please, tell me how to respond to this question!
>
Sorry, I wasn't clear. It sounds like you've got two very different
copy speeds on two possibly different data sets. The problem will be
significantly easier to debug and discuss if you boot a 2.4.19 + data
logging kernel, do the test, and then do the test again on a 2.4.21-pre
data logging kernel.
I know this is a pain, I want to reduce the number of variables in
place.
> P.S.: Do the data-logging things go to namesys now? (Me, watching Olegs
> recent engagements...)
Oleg is making patches for the -ac series. He also merged a special set
for Philippe, they pay namesys for support ;-)
I'm remerging my work over the last week and should have a new set of
patches out soon.
-chris
next prev parent reply other threads:[~2003-03-06 3:46 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-21 23:32 [PATCH] new data logging and quota patches available Chris Mason
2003-02-21 23:52 ` Philippe Gramoullé
2003-02-22 12:41 ` Dieter Nützel
2003-02-22 15:15 ` Chris Mason
2003-02-22 16:12 ` Chris Mason
2003-02-23 0:50 ` Manuel Krause
2003-02-23 1:04 ` Manuel Krause
2003-02-23 14:50 ` Chris Mason
2003-02-23 17:18 ` Chris Mason
2003-02-23 17:37 ` Marc-Christian Petersen
2003-02-23 18:39 ` Marc-Christian Petersen
2003-02-23 19:33 ` Chris Mason
2003-02-24 18:01 ` Marc-Christian Petersen
2003-02-24 1:42 ` Manuel Krause
2003-02-24 14:08 ` Chris Mason
2003-02-24 17:45 ` Manuel Krause
2003-02-24 22:19 ` Manuel Krause
2003-02-28 8:10 ` Manuel Krause
2003-02-28 13:32 ` Chris Mason
2003-03-06 2:49 ` Manuel Krause
2003-03-06 3:46 ` Chris Mason [this message]
2003-03-06 4:03 ` Manuel Krause
2003-03-08 14:13 ` Manuel Krause
2003-03-09 16:39 ` Chris Mason
2003-03-09 17:07 ` Manuel Krause
2003-03-09 17:24 ` Chris Mason
2003-03-09 17:39 ` Manuel Krause
2003-03-09 18:12 ` Chris Mason
2003-03-11 1:42 ` Chris Mason
2003-03-11 20:46 ` Chris Mason
2003-03-12 7:38 ` Oleg Drokin
2003-03-12 13:22 ` Chris Mason
2003-03-12 13:28 ` Oleg Drokin
2003-03-12 13:41 ` Chris Mason
2003-03-12 14:43 ` Manuel Krause
2003-03-12 14:55 ` Chris Mason
2003-03-12 19:25 ` Hans Reiser
2003-03-13 2:01 ` Manuel Krause
2003-02-24 17:59 ` Marc-Christian Petersen
2003-02-24 18:05 ` Marc-Christian Petersen
2003-02-24 18:46 ` Chris Mason
2003-02-24 18:08 ` Chris Mason
2003-02-24 18:11 ` Marc-Christian Petersen
2003-02-23 14:56 ` Chris Mason
2003-02-22 13:54 ` Oleg Drokin
2003-02-22 14:17 ` Chris Mason
2003-02-25 15:31 ` Ookhoi
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=1046922372.2161.275.camel@tiny.suse.com \
--to=mason@suse.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.