>
> Unfortunately, as the file grows, so does the VM Page Cache
> (and as a result the free memory on my system approaches 0!).
>
> For my application, I will *never* read back the file,
> and all file write operations will always be sequential.
>
> How can I either:
> 1) disable caching of such file system write-only operations
>    so that the VM Page Cache doesn't eat up memory?
> 2) Purge/shrink the VM Page Cache of all entries
>    for a particular vnode?  Is there a routine to do this?
>

i think somethink like in solaris - that large linearly accessed data has
lower priority and are removed from memory firsts.


and fcntl to give OS a hint file won't be needed again soon will be very
nice