All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Williams <Nicolas.Williams@oracle.com>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Queries regarding LDLM_ENQUEUE
Date: Wed, 20 Oct 2010 12:01:24 -0500	[thread overview]
Message-ID: <20101020170124.GT1635@oracle.com> (raw)
In-Reply-To: <4CBF1D00.9080402@psc.edu>

On Wed, Oct 20, 2010 at 12:46:56PM -0400, Paul Nowoczynski wrote:
> 
> > The name_to_handle() only needs to be called on a single node, and 
> > open_by_handle() is called on the other nodes. I agree that this 
> > doesn't avoid the full O(n) RPCs for the open itself  but at least it 
> > does avoid the full path traversal from every client and on the 
> > MDS (replacing it with an MPI broadcast of the handle).
> Andreas,
> excuse my ignorance, but why does open_by_handle() need to issue an 
> RPC?  If it's to obtain the layout, couldn't the layout be encoded into 
> the 'handle'?

If you don't mind having a huge handle, then yes, we could skip
additional RPCs.

A handle would have to consist of a {MGS address, FID, layout, access
type, capability}, or so.

  parent reply	other threads:[~2010-10-20 17:01 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-18 23:33 [Lustre-devel] Queries regarding LDLM_ENQUEUE Vilobh Meshram
2010-10-19 15:46 ` Fan Yong
2010-10-19 20:28 ` Vilobh Meshram
2010-10-19 22:53   ` Andreas Dilger
2010-10-20  2:04     ` Vilobh Meshram
2010-10-20  7:55       ` Andreas Dilger
2010-10-20  8:11         ` bzzz.tomas at gmail.com
2010-10-20  8:24           ` Andreas Dilger
2010-10-20  8:30             ` bzzz.tomas at gmail.com
2010-10-20  8:38               ` Nikita Danilov
2010-10-20 14:45                 ` Nicolas Williams
2010-10-20 13:30               ` Eric Barton
2010-10-20 13:40                 ` bzzz.tomas at gmail.com
2010-10-20 14:51                 ` Paul Nowoczynski
2010-10-20 14:55                   ` Nicolas Williams
2010-10-20 15:16                     ` Paul Nowoczynski
2010-10-20 16:07                       ` Andreas Dilger
2010-10-20 15:22                   ` bzzz.tomas at gmail.com
2010-10-20 16:43                     ` Paul Nowoczynski
2010-10-20 16:49                       ` bzzz.tomas at gmail.com
2010-10-20 17:11                         ` Paul Nowoczynski
2010-10-20 17:18                           ` bzzz.tomas at gmail.com
2010-10-20 17:25                             ` Paul Nowoczynski
2010-10-20 17:27                             ` Andreas Dilger
2010-10-20 17:29                             ` Nicolas Williams
2010-10-20 17:40                               ` bzzz.tomas at gmail.com
2010-10-20 18:01                                 ` Andreas Dilger
2010-10-20 18:09                                   ` bzzz.tomas at gmail.com
2010-10-20 16:35                 ` Andreas Dilger
2010-10-20 16:46                   ` Paul Nowoczynski
2010-10-20 17:00                     ` Andreas Dilger
2010-10-20 17:13                       ` Nicolas Williams
2010-10-20 17:30                         ` Andreas Dilger
2010-10-20 17:01                     ` Nicolas Williams [this message]
2010-10-22  2:33         ` Vilobh Meshram

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=20101020170124.GT1635@oracle.com \
    --to=nicolas.williams@oracle.com \
    --cc=lustre-devel@lists.lustre.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 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.