On Sun, Jul 19, 2015 at 02:25:14PM +0100, James Clarke wrote:
> Yeah, I tried inhibiting both buckets, but the paging RPCs still got through,
> so my guess was that libports's inhibit/resume methods weren't able to deal
> with libpager's own threads. The thing is I don't think we currently keep
Yeah, I tried inhibiting both buckets, but the paging RPCs still got through,
so my guess was that libports's inhibit/resume methods weren't able to deal
with libpager's own threads. The thing is I don't think we currently keep track
of any reference to the main/worker threads, as pager_start_wo
Hello James :)
Quoting James Clarke (2015-07-15 22:20:57)
> I had a look today at what's happening, and it's that the *file*
> pager is trying to read from disk. Any thoughts?
There is another thing I forgot. libpager is special, it has its own
demuxer (see libpager/demuxer.c) that writes reques
