From: Peter Braam <Peter.Braam@Sun.COM>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Re-direction inodes
Date: Mon, 02 Jun 2008 08:59:47 +0900 [thread overview]
Message-ID: <C4696703.566A%peter.braam@sun.com> (raw)
Hi Nikita -
I have a need in doing an architecture for a customer of a Lustre client
feature to have different data/page caches associated with an inode,
depending on the user that accesses it. So when a file is read, user A
will read different data from user B (assume the same for writes, but I
think this is a read-only feature).
I remember that in the Coda file system we could easily re-direct I/O to
another inode using almost standard features in the VFS/page caches. Is
this still the case? Would this work for the purpose I describe above?
Thanks.
Peter
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20080602/d39b9203/attachment.htm>
next reply other threads:[~2008-06-01 23:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-01 23:59 Peter Braam [this message]
2008-06-02 11:11 ` [Lustre-devel] Re-direction inodes Nikita Danilov
2008-06-02 12:07 ` Peter Braam
2008-06-02 17:09 ` Andreas Dilger
2008-06-04 1:17 ` Peter Braam
2008-06-04 9:11 ` Daire Byrne
2008-06-06 14:25 ` Canon, Richard Shane
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=C4696703.566A%peter.braam@sun.com \
--to=peter.braam@sun.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.