[lkml]   [2010]   [Oct]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] fs: inode per-cpu last_ino allocator

what workload did this matter for? As mentioned elsewhere we don't
actually need to set i_ino in new_inode in many cases. Normal
disk/network filesystem already set their own i_ino anyway and don't
need it at all. Various in-kernel filesystems don't need any valid
i_ino and Nick's full series actually has a patch dealing with it,
which only leaves various user-mountable syntetic filesystems that
want to generate an inode number, and IMHO they're better off using

 \ /
  Last update: 2010-10-03 23:01    [W:0.477 / U:0.116 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site