linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Kalpak Shah <kalpak@linsyssoft.com>,
	Karuna sagar K <karunasagark@gmail.com>, Amit Gud <gud@ksu.edu>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.orgG
Subject: Re: ChunkFS - measuring cross-chunk references
Date: Tue, 24 Apr 2007 11:07:43 -0400	[thread overview]
Message-ID: <20070424150743.GH1663@thunk.org> (raw)
In-Reply-To: <1177376549.3244.0.camel@laptopd505.fenrus.org>

On Mon, Apr 23, 2007 at 06:02:29PM -0700, Arjan van de Ven wrote:
> 
> > The other thing which we should consider is that chunkfs really
> > requires a 64-bit inode number space, which means either we only allow
> 
> does it?
> I'd think it needs a "chunk space" number and a 32 bit local inode
> number ;) (same for blocks)
> 

But that means that the number which gets exported to userspace via
the stat system call will need more than 32 bits worth of ino_t....

						- Ted


  parent reply	other threads:[~2007-04-24 15:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-22 20:35 ChunkFS - measuring cross-chunk references Karuna sagar K
2007-04-22 16:27 ` Amit Gud
2007-04-23  7:19   ` Karuna sagar K
2007-04-23  9:34     ` Kalpak Shah
2007-04-23 20:53       ` Andreas Dilger
2007-04-24  0:13         ` Theodore Tso
2007-04-24  1:02           ` Arjan van de Ven
2007-04-24  1:24             ` Amit Gud
2007-04-24  1:38               ` Amit Gud
2007-04-24 15:07             ` Theodore Tso [this message]
2007-04-25  0:17           ` Karuna sagar K
2007-04-25  0:20             ` Karuna sagar K
2007-04-25 10:23               ` Suparna Bhattacharya
2007-05-19 22:49                 ` Karuna sagar K
2007-05-07  5:18           ` Valerie Henson
2007-05-07  1:09         ` Valerie Henson
2007-05-07  1:09 ` Valerie Henson

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=20070424150743.GH1663@thunk.org \
    --to=tytso@mit.edu \
    --cc=arjan@infradead.org \
    --cc=gud@ksu.edu \
    --cc=kalpak@linsyssoft.com \
    --cc=karunasagark@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.orgG \
    /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).