linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Peter Rajnoha <prajnoha@redhat.com>
To: Chris Webb <chris@arachsys.com>
Cc: Richard Davies <richard.davies@elastichosts.com>,
	LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] devices.filter changed behaviour in 80ac8f37d6
Date: Mon, 7 Sep 2015 15:54:01 +0200	[thread overview]
Message-ID: <55ED96F9.8020809@redhat.com> (raw)
In-Reply-To: <B5E3ACA3-D8D1-49F5-A195-EE2345F4B79A@arachsys.com>

On 09/07/2015 03:44 PM, Chris Webb wrote:
> (I note from the pvscan(8) man page that global_filter applies to pvscan
> --cache but not standard filter, which sounds like another good reason
> to switch to global_filter!)

Yes, exactly. The idea behind filter and "global_filter" split is that
the global_filter applies globally on system scope (in our context of
lvmetad, it means lvmetad will see everything that "global_filter" allows,
not taking care about the "filter").

Then each LVM client (all LVM commands except pvscan --cache) can use
different "filter" for the information that lvmetad returns.

So you have two levels of filtering here: global one and client-side one
(that's exactly the split between "to update lvmetad" and
"to retrieve info from lvmetad" filter chain I described in my previous
post).

-- 
Peter

      reply	other threads:[~2015-09-07 13:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-05 11:56 [linux-lvm] devices.filter changed behaviour in 80ac8f37d6 Chris Webb
2015-09-07  7:30 ` Peter Rajnoha
2015-09-07 11:40   ` Peter Rajnoha
2015-09-07 11:48     ` Peter Rajnoha
2015-09-07 13:01     ` Chris Webb
2015-09-07 13:08       ` Chris Webb
2015-09-07 13:23         ` Peter Rajnoha
2015-09-07 13:35           ` Peter Rajnoha
2015-09-07 14:00             ` Chris Webb
2015-09-07 14:12               ` Peter Rajnoha
2015-09-07 13:14       ` Peter Rajnoha
2015-09-07 13:44         ` Chris Webb
2015-09-07 13:54           ` Peter Rajnoha [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=55ED96F9.8020809@redhat.com \
    --to=prajnoha@redhat.com \
    --cc=chris@arachsys.com \
    --cc=linux-lvm@redhat.com \
    --cc=richard.davies@elastichosts.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).