From: Javier Marcet <lists@marcet.info>
To: reiserfs-list@namesys.com
Cc: Dieter@marcet.info,
=?iso-8859-1?Q?N=FCtzel_=3CDieter=2ENuetzel=40hamburg=2Ede=3E?=@marcet.info,
"Chris Mason" <mason@suse.com>,
green@linuxhacker.ru, "Gerd Knorr" <kraxel@suse.de>,
"Jeff Mahoney" <jeffm@suse.com>
Subject: Re: v3 experimental data=ordered and logging speedups for 2.6.1
Date: Mon, 9 Feb 2004 15:14:01 +0100 [thread overview]
Message-ID: <20040209141401.GA30795@hiroshi> (raw)
In-Reply-To: <200402091404.40797.Dieter.Nuetzel@hamburg.de>
* Dieter Nützel <Dieter.Nuetzel@hamburg.de> [040209 14:00]:
>> > An EXPORT was missing in linux/fs/buffer.c to compile ReiserFS 3.x.x as
>> > modul (inode.c, unresolved symbol):
>> Thanks, I'll add it into the patch when I get back from linux world.
>More on this.
>I have now SuSE's 9.0 2.6.2-0 up and running.
>Only 01-reiserfs-journal-writer is needed now without modifications.
>02-reiserfs-nesting
>03-reiserfs-iosize
>04-reiserfs-balance_dirty
>Are all in an these two need some _little_ hand work:
>05-reiserfs-logging
>06-reiserfs-jh-2
>Don't forget this in fs/buffer.c
>EXPORT_SYMBOL(try_to_release_page);
Of the above, only 04-reiserfs-balance_dirty is included in vanilla
2.6.2. I applied the rest and I haven't had the smallest problem.
--
Javier Marcet <javier@marcet.info>
next prev parent reply other threads:[~2004-02-09 14:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 16:45 v3 experimental data=ordered and logging speedups for 2.6.1 Chris Mason
2004-01-19 22:53 ` Dieter Nützel
2004-01-19 22:54 ` Mike Fedyk
2004-01-21 1:50 ` Chris Mason
2004-02-09 13:04 ` Dieter Nützel
2004-02-09 14:14 ` Javier Marcet [this message]
2004-01-21 15:09 ` Oleg Drokin
2004-02-11 11:49 ` Oleg Drokin
2004-02-11 14:00 ` Chris Mason
2004-02-11 14:26 ` Oleg Drokin
2004-02-11 14:59 ` Chris Mason
2004-02-11 15:09 ` Oleg Drokin
2004-02-12 14:18 ` 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=20040209141401.GA30795@hiroshi \
--to=lists@marcet.info \
--cc==?iso-8859-1?Q?N=FCtzel_=3CDieter=2ENuetzel=40hamburg=2Ede=3E?=@marcet.info \
--cc=Dieter@marcet.info \
--cc=green@linuxhacker.ru \
--cc=javier@marcet.info \
--cc=jeffm@suse.com \
--cc=kraxel@suse.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.