Ooops....the time frame is closer to today on part of this. While it may
be a while before we hit the 1T limit on 1 single device, things like
readpage, do so based of the inode -- which on a metadisk could have a
filesize much larger than current physical device limits. So it seems
that at least at the vnode level this is something that may have to
go into the 2.4 series fairly soon, or am I missing something? Why
are blocks int's vs. unsigned's ? Was it to pass back errno's in some
cases?
-- Linda A Walsh | Trust Technology, Core Linux, SGI law@sgi.com | Voice: (650) 933-5338> It may not matter too too much, but blocks are being passed around as > 'ints'. On the ia32 architecture, this implies a maximum of 512*2G->1T > disk size. Probably don't need to worry about this today, but in a few > years? Should we be changing the internal interfaces to use a long (or > a long unsigned -- why signed?) Maybe for 2.5/2.6 timeframe? Just > curious...
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Aug 31 2000 - 16:15:29 EDT