Messages in this thread | | | Subject | Re: msync() behaviour broken for MS_ASYNC, revert patch? | From | "Stephen C. Tweedie" <> | Date | 01 Apr 2004 17:33:28 +0100 |
| |
Hi,
On Thu, 2004-04-01 at 17:02, Linus Torvalds wrote:
> > Worse, it doesn't seem to be implemented consistently either. I've been > > trying on a few other Unixen while writing this. First on a Tru64 box, > > and it is _not_ kicking off any IO at all for MS_ASYNC, except for the > > 30-second regular sync. The same appears to be true on FreeBSD. And on > > HP-UX, things go in the other direction: the performance of MS_ASYNC is > > identical to MS_SYNC, both in terms of observed disk IO during the sync > > and the overall rate of the msync loop. > > If you check HP-UX, make sure it's a recent one. HPUX has historically > been just too broken for words when it comes to mmap() (ie some _really_ > strange semantics, like not being able to unmap partial mappings etc).
I'm not sure what counts as "recent" for that, but this was on HP-UX 11. That's the most recent I've got access to.
--Stephen
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |