From: Marcos E. Matsunaga <Marcos.Matsunaga@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 0/3] Dynamic local alloc (halfway there)
Date: Wed, 13 Aug 2008 15:10:33 -0400 [thread overview]
Message-ID: <48A331A9.7000404@oracle.com> (raw)
In-Reply-To: <1217536922-28328-1-git-send-email-mfasheh@suse.com>
I ran tests on mainline.
The times in average goes up 3-4 times and then comes back to normal. I
had some hard times with the kernel because at some point it starts to
dump stacks for processes that stay too long without responding. Some of
the systems had times over 3-4 times going up to about 10 times, but my
guess is that it was related to the dumps as the systems get very slow
at that point.
I'm planning to leave it running again, but disabling the dumps. I'm not
really sure it will have much of an effect in terms of performance
impact, but I'll try.
Regards,
Marcos Eduardo Matsunaga
Oracle USA
Linux Engineering
?The statements and opinions expressed here are my own and do not
necessarily represent those of Oracle Corporation.?
Mark Fasheh wrote:
> The following patches against 2.6.26-rc1 implement the 1st part of dynamic
> local alloc support - allowing the allocator to shrink, and re-enable itself
> after being disabled. Growing the allocator beyond it's default will follow
> soon, once I have time to complete the implementation and testing. In the
> meantime, this series hopefully fixes at least one problem on long-running
> tests where the local alloc file gets disabled.
>
> Also included is a patch which adds a per-mountpoint debugfs file for
> tracking local alloc state. More state will be added to that patch once
> dynamic local alloc support is complete.
> --Mark
>
> _______________________________________________
> Ocfs2-devel mailing list
> Ocfs2-devel at oss.oracle.com
> http://oss.oracle.com/mailman/listinfo/ocfs2-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://oss.oracle.com/pipermail/ocfs2-devel/attachments/20080813/d66d0b12/attachment.html
next prev parent reply other threads:[~2008-08-13 19:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 20:41 [Ocfs2-devel] [PATCH 0/3] Dynamic local alloc (halfway there) Mark Fasheh
2008-07-31 20:42 ` [Ocfs2-devel] [PATCH 1/3] ocfs2: Track local alloc bits internally Mark Fasheh
2008-07-31 21:16 ` Joel Becker
2008-07-31 20:42 ` [Ocfs2-devel] [PATCH 2/3] ocfs2: throttle back local alloc when low on disk space Mark Fasheh
2008-07-31 21:11 ` Joel Becker
2008-07-31 20:42 ` [Ocfs2-devel] [PATCH 3/3] ocfs2: track local alloc state via debugfs Mark Fasheh
2008-07-31 21:16 ` Joel Becker
2008-08-13 19:10 ` Marcos E. Matsunaga [this message]
2008-08-13 19:52 ` [Ocfs2-devel] [PATCH 0/3] Dynamic local alloc (halfway there) Mark Fasheh
2008-08-13 20:47 ` Marcos E. Matsunaga
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=48A331A9.7000404@oracle.com \
--to=marcos.matsunaga@oracle.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.