From: Alexander Zarochentsev <zam@namesys.com>
To: Hans Reiser <reiser@namesys.com>
Cc: reiserfs-list@namesys.com, "Alec H. Peterson" <ahp@hilander.com>
Subject: Re: Reiser4 unlink performance
Date: Wed, 1 Mar 2006 00:22:29 +0300 [thread overview]
Message-ID: <200603010022.29721.zam@namesys.com> (raw)
In-Reply-To: <4404B5C5.3090702@namesys.com>
On Tuesday 28 February 2006 23:42, Hans Reiser wrote:
> Alexander Zarochentsev wrote:
> >On Tuesday 28 February 2006 22:56, Hans Reiser wrote:
> >>Alexander Zarochentsev wrote:
> >>>On Tuesday 28 February 2006 22:11, Hans Reiser wrote:
> >>>>Alec H. Peterson wrote:
> >>>>>Hi Alexander,
> >>>>>
> >>>>>On Feb 26, 2006, at 13:42, Alexander Zarochentsev wrote:
> >>>>>>Which kernel version and reiser4 patches were used?
> >>>>>
> >>>>>2.6.15.4r4 kernel,
> >>>>>reiser4-for-2.6.15-1.patch
> >>>>>
> >>>>>>Is the system SMP?
> >>>>>
> >>>>>Yes.
> >>>>>
> >>>>>>No, "Flushing like mad" usually indicates a bug.
> >>>>
> >>>>Please describe it in more detail.
> >>>
> >>>The flush algorithm designed to make progress in any iteration.
> >>>"flushing like mad" messages usually indicates that the flush
> >>> can't make progress.
> >>
> >>Yet more detail please.
> >
> >the algorithm does not work as designed, it is a design bug or an
> >implementation bug ;)
>
> I seem to remember vs saying this message could be ignored safely at
> times in the past, which is why I am asking you for more details.
We have improved handling of truncate/flush races, especially if
formatted nodes are deleted. Now I think that any truncate/flush race
can be resolved w/o having those too many useless iterations of
jnode_flush.
> Hans
--
Alex.
prev parent reply other threads:[~2006-02-28 21:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 14:33 Reiser4 unlink performance Alec H. Peterson
[not found] ` <200602262342.23069.zam@namesys.com>
2006-02-28 14:51 ` Alec H. Peterson
2006-02-28 19:11 ` Hans Reiser
2006-02-28 19:19 ` Alec H. Peterson
2006-02-28 19:43 ` Hans Reiser
2006-03-01 15:27 ` Alexander Zarochentsev
2006-03-01 15:34 ` Alec H. Peterson
2006-02-28 19:48 ` Alexander Zarochentsev
2006-02-28 19:56 ` Hans Reiser
2006-02-28 20:06 ` Alexander Zarochentsev
2006-02-28 20:42 ` Hans Reiser
2006-02-28 21:22 ` Alexander Zarochentsev [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=200603010022.29721.zam@namesys.com \
--to=zam@namesys.com \
--cc=ahp@hilander.com \
--cc=reiser@namesys.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.