From: DENIEL Philippe <philippe.deniel@CEA.FR>
To: xfs@oss.sgi.com
Subject: Question : Using libhandle from xfsprogs and xfs actions made "by handle"
Date: Wed, 05 May 2010 15:54:59 +0200 [thread overview]
Message-ID: <4BE178B3.8030501@cea.fr> (raw)
Hi,
I had a look at the stuff within xfsprogs and it really look pretty
nice. One thing is of great interest to me : the libhandle.so library.
I am currently developing a NFS server running in userspace (see
http://nfs-ganesha.sourceforge.net for details). As you know, the NFS
protocol has a "handle based" semantics in the way it manages FS
objects. All objects are identified by a unique filehandle or by their
name and the parent's directory filehandle. The trouble is that libC
does not include such "by handle" calls to manage FS, only the old
fashioned POSIX API which is a "By path" API.
When looking at XFS, I saw there was "open_by_handle" and
"path_to_handle" calls. This sounds very very good to me : this sounds
like kind of bridge to build a handle-based API to address XFS. But so
far, I am a bit stuck : for exporting XFS through my NFS server, I would
need to do "by handle" everything that can be done through POSIX calls,
open/read/write/close files, create files/directories/symlinks, erasing
or moving files... and so on. I do not know if this is possible with the
calls in libhandle.so. But if I had such handle based tools, I think I
could make a nice NFS server on top of XFS (I did this kind of port for
LUSTRE (which has a full handle based API) in my NFS server and I had
really good performances). Can someone provide me with information about
this ?
Regards
Philippe
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2010-05-05 13:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 13:54 DENIEL Philippe [this message]
2010-05-06 20:35 ` Question : Using libhandle from xfsprogs and xfs actions made "by handle" Christoph Hellwig
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=4BE178B3.8030501@cea.fr \
--to=philippe.deniel@cea.fr \
--cc=xfs@oss.sgi.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