On Tue, 22 May 2001, Peter Wemm wrote:
John Baldwin wrote:
If I have swap (i.e. I've run swapon on a swap partition) the program is kill
ed
by the system fine. If I don't have swap, then both the memkill process adn
the swapper process (proc0) are stuck in the vmwait wait channel
On 20-May-01 Alfred Perlstein wrote:
I broke swapping with the vm mutex.
Hopefully I should have this fixed up within a couple of days tops.
No, I'm not heading off to Aruba or someplace after this intrusive
change, I am working on it. Your kernel may panic, but I hope you
all keep a
On 22-May-01 John Baldwin wrote:
On 20-May-01 Alfred Perlstein wrote:
I broke swapping with the vm mutex.
Hopefully I should have this fixed up within a couple of days tops.
No, I'm not heading off to Aruba or someplace after this intrusive
change, I am working on it. Your kernel may
On 22-May-01 John Baldwin wrote:
On 20-May-01 Alfred Perlstein wrote:
I broke swapping with the vm mutex.
Hopefully I should have this fixed up within a couple of days tops.
No, I'm not heading off to Aruba or someplace after this intrusive
change, I am working on it. Your kernel may
John Baldwin wrote:
If I have swap (i.e. I've run swapon on a swap partition) the program is kill
ed
by the system fine. If I don't have swap, then both the memkill process adn
the swapper process (proc0) are stuck in the vmwait wait channel used by
VM_WAIT. Any ideas?
This may not be
I broke swapping with the vm mutex.
Hopefully I should have this fixed up within a couple of days tops.
No, I'm not heading off to Aruba or someplace after this intrusive
change, I am working on it. Your kernel may panic, but I hope you
all keep a level head about this and don't follow suit.
