On Wednesday 25 February 2009 16:36:39 Scott Seekamp wrote:

> I did search and it did not return any results.

They should really kill the htdig project already ;)

> That is helpful, but I was hoping to get an indication of what the
> effects of changing this setting and what is the maximum before looking
> elsewhere for changes?

Your system might be wanting more then the system can offer. It's further 
explained here:

Quoting Mark Tinguely:
> Sometimes pv_entry allocation can fail even below the pv_entry_high_water
> if there is no more free pages available to allocate for a pv_entry chunk.
> Operations (such temp mappings, copies) will not occur if the
> pv_entry_high_water (90% if pv_entry_max) has been reached OR a
> page is not immediately available for allocation.

I don't know what the max is. If you have to increase it a lot, f.e. >500%, 
then either the default is porely chosen, you demand a lot or your system is 
doing things it's not supposed to do. I would slowly increase it to insane 
ammounts. If it never goes away and load of the machine isn't shocking, then 
this might be a bug. Either way, there aren't too many tools to diagnose this 
problem. Maybe procstat(8) -v should give some insight.

Problem with today's modular software: they start with the modules
    and never get to the software part.
freebsd-questions@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Reply via email to