Re: [PATCH 00/29] Swap over NFS -v15
On Wed, 2007-12-19 at 17:22 -0500, Bill Davidsen wrote: > Peter Zijlstra wrote: > > Hi, > > > > Another posting of the full swap over NFS series. > > > > Andrew/Linus, could we start thinking of sticking this in -mm? > > > > Two questions: > 1 - what is the memory use impact on the system which don't do swap over > NFS, such as embedded systems, and It should have little to no impact if not used. > 2 - what is the advantage of this code over the two existing network > swap approaches, > swapping to NFS mounted file and This is not actually possible with a recent kernel, current swapfile support requires a blockdevice. > swap to NBD device? > I've used the NFS file when a program was running out of memory and that > seemed to work, people in UNYUUG have reported that the nbd swap works, > so what's better here? swap over NBD works sometimes, its rather easy to deadlock, and its impossible to recover from a broken connection. signature.asc Description: This is a digitally signed message part
Re: [PATCH 00/29] Swap over NFS -v15
Peter Zijlstra wrote: Hi, Another posting of the full swap over NFS series. Andrew/Linus, could we start thinking of sticking this in -mm? Two questions: 1 - what is the memory use impact on the system which don't do swap over NFS, such as embedded systems, and 2 - what is the advantage of this code over the two existing network swap approaches, swapping to NFS mounted file and swap to NBD device? I've used the NFS file when a program was running out of memory and that seemed to work, people in UNYUUG have reported that the nbd swap works, so what's better here? -- Bill Davidsen <[EMAIL PROTECTED]> "We have more to fear from the bungling of the incompetent than from the machinations of the wicked." - from Slashdot -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 00/29] Swap over NFS -v15
Hi Peter, A major feature of this patch set is the network receive deadlock avoidance, but there is quite a bit of stuff bundled with it, the NFS user accounting for a big part of the patch by itself. Is it possible to provide a before and after demonstration case for just the network receive deadlock part, given a subset of the patch set and a user space recipe that anybody can try? Regards, Daniel -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
