Subject: Re: jerky interactive behavior -- a clue?
To: George Michaelson <ggm@apnic.net>
From: Blair Sadewitz <blair.sadewitz@gmail.com>
List: current-users
Date: 01/30/2007 16:05:47
The problem with BUFQ_PRIOCSCAN, I found out, is that--at least at the
time it was written--there was no way to speed the writing of pages
queued for delayed write.  Thus, VOP_GETPAGES would wait on them until
the cache was flushed, regardless of whether or not they could be
freed at that moment.
I could imagine things getting very nasty with BUFQ_PRIOCSCAN during
memory-starved, high-I/O situations.

Does anyone know if this is still the case?

Regards,

--Blair


-- 
Support WFMU-FM: free-form radio for the masses!

<http://www.wfmu.org/>
91.1 FM Jersey City, NJ
90.1 FM Mt. Hope, NY

"The Reggae Schoolroom":
<http://www.wfmu.org/playlists/RS/>