All of lore.kernel.org
 help / color / mirror / Atom feed
From: bzzz.tomas at gmail.com <bzzz.tomas@gmail.com>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Queries regarding LDLM_ENQUEUE
Date: Wed, 20 Oct 2010 12:11:01 +0400	[thread overview]
Message-ID: <4CBEA415.80307@gmail.com> (raw)
In-Reply-To: <EF473480-D749-4AF4-B843-697A2EDE10A2@oracle.com>

On 10/20/10 11:55 AM, Andreas Dilger wrote:
> There is a separate proposal that has been underway in the Linux community for some time, to allow a user process to get a file handle (i.e. binary blob returned from a new name_to_handle() syscall) from the kernel for a given pathname, and then later use that file handle in another process to open a file descriptor without re-traversing the path.
>
> I've been thinking this would be very useful for Lustre (and MPI in general), and have tried to steer the Linux development in a direction that would allow this to happen.  Is this in line with what you are investigating?

with FIDs is quite possible and even safe if application can learn it
(using xattr_get or ioctl). then it should be trivial to export FID
namespace on MDS via special .lustre-fids directory?

another idea was to do whole path traversal on MDS within a single RPC.
bug that'd require amount of changes to llite and/or VFS and keep MDS
a bottleneck.

thanks, z

  reply	other threads:[~2010-10-20  8:11 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 [this message]
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
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=4CBEA415.80307@gmail.com \
    --to=bzzz.tomas@gmail.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.