Re: [PATCH 18/18] fs: do not assign default i_ino in new_inode

[Christoph Hellwig]

On Sat, Oct 16, 2010 at 06:57:28PM +1100, Nick Piggin wrote:
> My patch for this reduces churn by just adding a new function instead.
> The last_ino allocator is really fast now, so IMO it was not worth
> the churn to go through filesystems; just let them do it.

See the last comment on this.  Allocating an inode and assigning a badly
made up ino for a handfull synthetic filesystems are very different
things.  Mixing them up in one function always was a bad idea.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/