From: Fabio Massimo Di Nitto <fabbione@ubuntu.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 0/3] Properly protect the extent map
Date: Mon Apr 2 11:48:17 2007 [thread overview]
Message-ID: <46114FE6.8030704@ubuntu.com> (raw)
In-Reply-To: <20070402184550.GA21982@ca-server1.us.oracle.com>
Mark Fasheh wrote:
> On Thu, Mar 29, 2007 at 10:38:24AM +0200, Fabio Massimo Di Nitto wrote:
>> on all 3 of them. They fix the problem as i reported it, but it looks like they
>> introduce a performance hit.
>
> Can you elaborate on that please?
>
> I don't see anything in those patches that should cause any performance
> problems but if you have any more information about what you saw, it might
> point to something we missed.
> --Mark
>
Hi Mark,
i kept logging all the info in the bug:
http://oss.oracle.com/bugzilla/show_bug.cgi?id=859
Fabio
--
I'm going to make him an offer he can't refuse.
next prev parent reply other threads:[~2007-04-02 11:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-28 18:50 [Ocfs2-devel] [PATCH 0/3] Properly protect the extent map Joel Becker
2007-03-28 18:50 ` [Ocfs2-devel] [PATCH 1/3] ocfs2: Wrap access of directory allocations with ip_alloc_sem Joel Becker
2007-03-28 18:51 ` [Ocfs2-devel] [PATCH 3/3] ocfs2: Local mounts should not truncate the extent map Joel Becker
2007-03-28 18:51 ` [Ocfs2-devel] [PATCH 2/3] ocfs2: Properly lock extent map size changes Joel Becker
2007-03-29 2:04 ` [Ocfs2-devel] [PATCH 0/3] Properly protect the extent map Fabio Massimo Di Nitto
2007-03-29 9:41 ` Sunil Mushran
2007-04-02 11:45 ` Mark Fasheh
2007-04-02 11:48 ` Fabio Massimo Di Nitto [this message]
2007-04-02 11:58 ` Mark Fasheh
2007-04-02 12:00 ` Fabio Massimo Di Nitto
2007-04-02 11:47 ` Mark Fasheh
2007-04-02 16:55 ` Joel Becker
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=46114FE6.8030704@ubuntu.com \
--to=fabbione@ubuntu.com \
--cc=ocfs2-devel@oss.oracle.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.