Volatile ranges with fallocate()

So I moved from madvise to fadvise early on because the need to be able to coordinate shared volatile ranges between processes, in the fashion ashmem provides.

That said, once the backing infrastructure for fallocate() volatile regions is upstream, there isn't a reason why a simpler madvise interface wouldn't also be viable.

I'd invite you to join the discussion on lkml to further discuss this.