From: Fionn Behrens <fionn@spamfilter.de>
To: reiserfs-list@namesys.com
Subject: Re: reiser4 in 2.6.14 - lockups with mmapped files
Date: Thu, 03 Nov 2005 15:30:06 +0100 [thread overview]
Message-ID: <1131028204.13284.29.camel@laptop> (raw)
In-Reply-To: <436796F6.10603@namesys.com>
[-- Attachment #1: Type: text/plain, Size: 706 bytes --]
In the mean time I mailed the archck patch maintainer and he readily
acknowledged that his reiser4 patch is flawed. He recommended that I
should apply the "*-2" patches from
ftp.namesys.com/pub/reiser4-for-2.6/2.6.14-rc4-mm1 . Unfortunately the
spinlock-2 patch wont apply cleanly but has seven failed hunks. Since I
have no idea how relevant these patches are I wanted to ask again
whether I should try to fix that patch or just leave it for now and try
the USE_EFLUSH(1) solution first? What would be the most effective
approach?
br,
Fionn
--
New laws should have better reasons than "recommended by lawyers"
and "they handle it the same way in the US". *** Lawrence Lessig
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-11-03 14:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 15:50 reiser4 in 2.6.14 - lockups with mmapped files Fionn Behrens
2005-11-01 16:25 ` Vladimir V. Saveliev
2005-11-01 17:41 ` Fionn Behrens
2005-11-01 19:37 ` Sander
2005-11-03 14:30 ` Fionn Behrens [this message]
2005-11-03 15:21 ` Vladimir V. Saveliev
2005-11-03 20:17 ` jp
2005-11-04 16:19 ` Vladimir V. Saveliev
2005-11-04 19:38 ` jp
2005-11-12 1:58 ` rvalles
[not found] ` <20051112015840.GA28777@148.Red-217-126-33.pooles.rima-tde.net.>
2005-11-12 15:13 ` Artur Makówka
2005-11-15 8:12 ` Vladimir V. Saveliev
2005-11-04 21:12 ` SOLVED: " Fionn Behrens
2005-11-09 0:21 ` rvalles
[not found] ` <20051109002158.GA21403@148.Red-217-126-33.pooles.rima-tde.net.>
2005-11-09 8:25 ` Raymond A. Meijer
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=1131028204.13284.29.camel@laptop \
--to=fionn@spamfilter.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.