News for hackers. Stuff that matters.
Re:C Craft by mbreese on Friday December 18, 2009 @12:54PM (#1003551)
I'm curious: are the standard IO functions that much more efficient than a mmap'd file? What makes you choose one over the other?

I usually just use standard IO, unless I have a large file that might be randomly accessed by multiple processes. In that case I'll use a mmap. But, I don't code in C very much anymore, so I was wondering how much of a difference there really is.

Re:C Craft by sorbits on Sunday December 20, 2009 @12:07PM (#1006303)
I did benchmarks on OS X (10.5) between asynchronous IO, mmap, stdio, and normal unix open/read (disabling caching) — it all came down to about the same after I had fiddled with page size, prefetch size, etc. to optimize each.

This of course depends on your OS (and version). My advice would be to pick API based on “semantics” (or need for portability). If you need to read through a file, use the API intended for that because mmap will not be optimized for that access pattern, but stdio will.

Re:C Craft by Locke1689 on Friday December 18, 2009 @08:39PM (#1004377)
Mostly because mmap is not portable. If you're writing a Linux specific version of your code then mmap is fine. If you foresee running your code on other platforms then you shouldn't use it.

Basically, there's a reason why it's called "standard" IO. Generally you shouldn't use system calls unless you are absolutely, 100% sure that your code will only ever need to work on one system.

Re:C Craft by holygoat on Friday December 18, 2009 @08:53PM (#1004391)
I've worked on a project that successfully uses memory mapping on all the major OSes.

mmap is (allegedly) portable across Unixes:

http://opengroup.org/onlinepubs/007908775/xsh/mmap.html

and you can do the same thing (with a few more hoops) on Windows.

Re:C Craft by kelnos on Saturday December 19, 2009 @04:32AM (#1004630)
Many people may not care, but mmap() often doesn't exist on hardware without a MMU.
Re:C Craft by Locke1689 on Friday December 18, 2009 @10:21PM (#1004446)
There's no guarantee that it will be portable and act the same (even across the POSIX systems). I'm not saying you should never use it, just that it shouldn't your automatic answer to everything.