From: Sunil Mushran <sunil.mushran@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 5/5] ocfs2: Disable orphan scanning for local and hard-ro mounts
Date: Mon, 22 Jun 2009 13:26:40 -0700 [thread overview]
Message-ID: <4A3FE900.30405@oracle.com> (raw)
In-Reply-To: <20090622192509.GB3902@mail.oracle.com>
Joel Becker wrote:
> On Mon, Jun 22, 2009 at 11:40:07AM -0700, Sunil Mushran wrote:
>> Local and Hard-RO mounts do not need orphan scanning.
> I just realized that we hold the os->os_lock around everything
> we do here. The orphan scan state doesn't need to be atomic_t.
No we don't hold it across all ops. In ocfs2_orphan_scan_stop(), we set
it inactive before taking the mutex. This allows ocfs2_queue_orphan_scan()
to bail out without queuing the tasks. The idea is to prevent umount
slowdown
- as much as possible.
next prev parent reply other threads:[~2009-06-22 20:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 18:40 [Ocfs2-devel] Orphan Scan - v3 Sunil Mushran
2009-06-22 18:40 ` [Ocfs2-devel] [PATCH 5/5] ocfs2: Disable orphan scanning for local and hard-ro mounts Sunil Mushran
2009-06-22 19:25 ` Joel Becker
2009-06-22 20:26 ` Sunil Mushran [this message]
2009-06-22 21:06 ` Joel Becker
2009-07-07 20:46 ` Jeff Mahoney
2009-07-07 21:08 ` Sunil Mushran
2009-07-07 21:22 ` Jeff Mahoney
2009-07-07 21:31 ` Sunil Mushran
2009-07-10 0:51 ` Joel Becker
-- strict thread matches above, loose matches on Subject: below --
2009-06-19 23:53 [Ocfs2-devel] Orphan scan fixes - V2 Sunil Mushran
2009-06-19 23:53 ` [Ocfs2-devel] [PATCH 5/5] ocfs2: Disable orphan scanning for local and hard-ro mounts Sunil Mushran
2009-06-20 4:41 ` Joel Becker
2009-06-20 4:57 ` Sunil Mushran
2009-06-22 16:17 ` Joel Becker
2009-06-22 17:26 ` Sunil Mushran
2009-06-19 21:45 [Ocfs2-devel] [PATCH 1/5] ocfs2: Pin journal head before accessing jh->b_committed_data Sunil Mushran
2009-06-19 21:45 ` [Ocfs2-devel] [PATCH 5/5] ocfs2: Disable orphan scanning for local and hard-ro mounts Sunil Mushran
2009-06-19 22:01 ` 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=4A3FE900.30405@oracle.com \
--to=sunil.mushran@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.