From: Christoph Hellwig <hch@infradead.org>
To: David Chinner <dgc@sgi.com>
Cc: xfs-dev <xfs-dev@sgi.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [Patch] unique per-AG inode generation number initialisation
Date: Mon, 7 Apr 2008 08:57:38 -0400 [thread overview]
Message-ID: <20080407125738.GD27350@infradead.org> (raw)
In-Reply-To: <20080401231815.GW103491721@sgi.com>
I don't really like this. The chance to hit a previously used
generation seems to high. What about making the first few bits
of each generation number a per-ag counter that's incremented anytime
we deallocate an inode cluster?
next prev parent reply other threads:[~2008-04-07 12:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 23:18 [Patch] unique per-AG inode generation number initialisation David Chinner
2008-04-02 4:02 ` Niv Sardi
2008-04-04 9:08 ` Hans-Peter Jansen
2008-04-07 12:57 ` Christoph Hellwig [this message]
2008-04-07 21:52 ` David Chinner
2008-04-10 4:34 ` David Chinner
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=20080407125738.GD27350@infradead.org \
--to=hch@infradead.org \
--cc=dgc@sgi.com \
--cc=xfs-dev@sgi.com \
--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