From: "Peter J. Braam" <braam@clusterfs.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
phil@off.net
Subject: Re: tmpfs, NFS, file handles
Date: Wed, 20 Feb 2002 12:21:16 -0700 [thread overview]
Message-ID: <20020220122116.C28913@lustre.cfs> (raw)
In-Reply-To: <20020220094649.X25738@lustre.cfs> <3C73D548.648C5D64@mandrakesoft.com>
In-Reply-To: <3C73D548.648C5D64@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Wed, Feb 20, 2002 at 11:56:40AM -0500
Hi,
> "Peter J. Braam" wrote:
...
> > Is there a suggested solution for fh_to_dentry and dentry_to_fh for
> > tmpfs?
> >
> > An "iget" based solution might work but at present tmpfs inodes are
> > not hashed.
On Wed, Feb 20, 2002 at 11:56:40AM -0500, Jeff Garzik wrote:
...
> I talked to neil brown about NFS and ramfs... he mentioned using
> iunique()
So do I understand that hashing tmpfs inodes is perhaps the way to go?
Would the following also work?
- have a 32 bit counter: set inode->i_ino to count++
- up the generation number each time the counter warps.
Between boot cycles NFS could still get confused, that might be helped
by setting the initial generation to the system time.
Thoughts anyone?
- Peter -
next prev parent reply other threads:[~2002-02-20 19:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-20 16:46 tmpfs, NFS, file handles Peter J. Braam
2002-02-20 16:56 ` Jeff Garzik
2002-02-20 19:21 ` Peter J. Braam [this message]
2002-02-20 19:42 ` Trond Myklebust
2002-02-20 22:53 ` Neil Brown
2002-02-21 4:43 ` David Chow
2002-02-21 5:04 ` Neil Brown
[not found] ` <3C790FB2.50503@rcn.com.hk>
2002-02-24 21:49 ` Neil Brown
2002-02-21 7:40 ` Christoph Rohland
-- strict thread matches above, loose matches on Subject: below --
2002-02-21 16:16 Lever, Charles
2002-02-21 22:58 ` Neil Brown
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=20020220122116.C28913@lustre.cfs \
--to=braam@clusterfs.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phil@off.net \
/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