From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org,
san-UZOCzndLCy9BDgjK7y7TUQ@public.gmane.org
Subject: Re: Constant checkpointing and cleanerd activity - doesn't play nice with mount --bind ?
Date: Wed, 01 Apr 2009 01:09:51 +0900 (JST) [thread overview]
Message-ID: <20090401.010951.130984382.ryusuke@osrg.net> (raw)
In-Reply-To: <591bc86b0903310814t2814ab95ie71077d5bb59f99d-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi,
On Tue, 31 Mar 2009 15:14:48 +0000, Alex Bitney <san-UZOCzndLCy9BDgjK7y7TUQ@public.gmane.org> wrote:
> On Tue, Mar 31, 2009 at 3:10 PM, Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org> wrote:
>
> > On Tue, 31 Mar 2009 23:44:37 +0900 (JST), Ryusuke Konishi <
> > ryusuke-sG5X7nlA6pw@public.gmane.org> wrote:
> >
> > Let me add one thing. Since the bind-mount and original r/w-mount
> > share the same device, only one cleanerd is enough for them. (In
> > fact, two cleanerds conflict with one another). So, we can give over
> > the GC functionality to the original mount point without incident.
>
>
> Just a question; why can't you use single cleaner? It would detect all
> mounted partitions and perform needed tasks, maybe in parallel, as needed.
Well, single (shared) cleanerd approach indeed sounds better in the
long term. The merit of the current pid and signal based (individual
cleaner) approach is its simplicity. So, I think we should make the
shift to the single cleaner approach if things get unmanageable within
the current way.
The reason why we are not using the shared cleaner, is just we took
the present way when we first designed it.
Regards,
Ryusuke Konishi
prev parent reply other threads:[~2009-03-31 16:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 10:45 Constant checkpointing and cleanerd activity - doesn't play nice with mount --bind ? Roman Mamedov
[not found] ` <20090317154529.1aeeecdc-2Ve/5xEMxL0@public.gmane.org>
2009-03-17 13:43 ` Ryusuke Konishi
[not found] ` <20090317.224324.58871500.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-03-17 14:19 ` Roman Mamedov
[not found] ` <20090317191924.1924576b-2Ve/5xEMxL0@public.gmane.org>
2009-03-22 17:53 ` Ryusuke Konishi
2009-03-31 14:44 ` Ryusuke Konishi
[not found] ` <20090331.234437.112904649.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-03-31 15:10 ` Ryusuke Konishi
[not found] ` <20090401.001059.06956465.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-03-31 15:14 ` Alex Bitney
[not found] ` <591bc86b0903310814t2814ab95ie71077d5bb59f99d-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-03-31 16:09 ` Ryusuke Konishi [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=20090401.010951.130984382.ryusuke@osrg.net \
--to=ryusuke-sg5x7nla6pw@public.gmane.org \
--cc=san-UZOCzndLCy9BDgjK7y7TUQ@public.gmane.org \
--cc=users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox