From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH] GFS2: eliminate i_generation from memory
Date: Wed, 23 Mar 2011 09:55:45 -0400 (EDT) [thread overview]
Message-ID: <644917506.564682.1300888545934.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com> (raw)
In-Reply-To: <1300888211.2590.41.camel@dolmen>
----- Original Message -----
| Hi,
|
| We still need that, it is the generation number for NFS. Although it
| is
| also identical to the no_formal_ino in recent kernels,
|
| Steve.
Are you saying that nfs manipulates gfs2's i_generation value in
the incore gfs2_inode structure? If so, that scares me; there
should be an interface to do that. If not, it must be for some
future development, because we don't reference the value anywhere.
Regards,
Bob Peterson
Red Hat File Systems
next prev parent reply other threads:[~2011-03-23 13:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 13:37 [Cluster-devel] [GFS2 PATCH] GFS2: eliminate i_generation from memory Bob Peterson
2011-03-23 13:50 ` Steven Whitehouse
2011-03-23 13:55 ` Bob Peterson [this message]
2011-03-23 14:04 ` Steven Whitehouse
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=644917506.564682.1300888545934.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com \
--to=rpeterso@redhat.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;
as well as URLs for NNTP newsgroup(s).