From: Andrew Morton <akpm@linux-foundation.org>
To: stefani@seibold.net
Cc: linux-kernel@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] cramfs: generate unique inode number for better inode cache usage
Date: Tue, 14 Dec 2010 12:51:43 -0800 [thread overview]
Message-ID: <20101214125143.0ab00c97.akpm@linux-foundation.org> (raw)
In-Reply-To: <1292150923-25586-1-git-send-email-stefani@seibold.net>
On Sun, 12 Dec 2010 11:48:42 +0100
stefani@seibold.net wrote:
> This patch generates a unique inode numbers for any entries in the cram file
> system. For files which did not contain data's (device nodes, fifos and
> sockets) the offset of the directory entry inside + 1 will be used as the
> inode number.
>
> The + 1 for the inode will it make possible to distinguish between
> a file which contains no data and files which has data, the later one has
> a inode value where the lower two bits are always 0.
>
> It also reimplement the behavoir to set the size and the number of block
> to 0 for special file, which is the right value for devices, fifos and
> sockets.
>
> As a little benefit it will be also more compatible which older
> mkcramfs, because it will never use the cramfs_inode->offset for
> creating a inode number for special files.
Did you look at using iunique() to generate cramfs inode numbers?
next prev parent reply other threads:[~2010-12-14 20:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-12 10:48 [PATCH] cramfs: generate unique inode number for better inode cache usage stefani
2010-12-14 20:51 ` Andrew Morton [this message]
2010-12-14 21:02 ` Stefani Seibold
2010-12-14 21:12 ` Andrew Morton
2010-12-14 21:27 ` Stefani Seibold
2010-12-14 21:08 ` Linus Torvalds
2010-12-14 21:24 ` Stefani Seibold
-- strict thread matches above, loose matches on Subject: below --
2010-12-14 23:12 stefani
2010-12-14 23:32 ` Linus Torvalds
2010-12-14 23:43 ` Linus Torvalds
2010-12-15 7:50 ` Stefani Seibold
2010-12-15 8:15 ` Pekka Enberg
2010-12-15 15:51 ` Linus Torvalds
2010-12-15 16:31 ` stefani
2010-12-15 16:45 ` Linus Torvalds
2010-12-16 9:47 ` Stefani Seibold
2010-12-16 9:52 stefani
2010-12-16 11:45 ` Pekka Enberg
2010-12-16 16:40 stefani
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=20101214125143.0ab00c97.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stefani@seibold.net \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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.