All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Rajnoha <prajnoha@redhat.com>
To: lvm-devel@redhat.com
Subject: [PATCH] Introduce immediate_dev_node flag for dm tree items to support immediate node creation on demand
Date: Tue, 08 Jun 2010 15:11:20 +0200	[thread overview]
Message-ID: <4C0E4178.4010300@redhat.com> (raw)
In-Reply-To: <4C0E371F.5020507@redhat.com>

On 06/08/2010 02:27 PM, Peter Rajnoha wrote:
> So let's use a flag (or "load_property") called "immediate_dev_node" for such a dm tree
> node which triggers immediate synchronisation with udev and node creation when needed.

Just one thing to add. For now, the flag is checked for in
dm_tree_preload_children only! It's debatable whether we need
something like that in dm_tree_{activate, deactivate}_children...

And if yes, do we need to differentiate among these situations?

Peter



  reply	other threads:[~2010-06-08 13:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-08 12:27 [PATCH] Introduce immediate_dev_node flag for dm tree items to support immediate node creation on demand Peter Rajnoha
2010-06-08 13:11 ` Peter Rajnoha [this message]
2010-06-17 22:15 ` Jonathan Brassow

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=4C0E4178.4010300@redhat.com \
    --to=prajnoha@redhat.com \
    --cc=lvm-devel@redhat.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.