>Until you modify the map, an exclusive lock on the map is overkill. Try >using read locks. (See vm_map_lookup.) > >In the meantime, I can't see any reason why mincore acquires an >exclusive lock either. (It never modifies the map.) I'm going >to remedy that.
Doesn't it modify the map indirectly vi subyte()? I think it wants to prevent modifications, but this is impossible. Bruce To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
