On Fri, Jun 11, 2010 at 7:30 PM, pancake <panc...@youterm.com> wrote: > Not really. Actually NOBODY reads files bigger than 2GB in a SINGLE syscall. > > Such operation would lock the process for a long and eat so many resorces > from the app (it should malloc 2GB.. Or use mmap which is a kernel wrap for > tis in a cached way over.. But certainly mmaping more than 2GB can be > problematic..mostly because of architecture (x86) limits in mmu. So u will > probably end up overwritting over mmaped stuff on the same virtual memory > space of the app. > > this is why i said it was a silly example. > > Think before posting or blaming ;)
Think before posting or blaming. 2GB might be silly now, much as 2MB was silly 20 years ago. I can't see why it would be extraordinarily silly to read in/map 2GB from a file 10 years from now. It takes 10 seconds at most *today*. And to limit your application because people still use a broken processor architecture sounds a bit windows-y I think..
