On Mon, 20 Jun 2011 14:12:06 +0100 Mel Gorman <mgorman@xxxxxxx> wrote: > Swapping over NBD is something that is technically possible but not > often advised. While there are number of guides on the internet > on how to configure it and nbd-client supports a -swap switch to > "prevent deadlocks", the fact of the matter is a machine using NBD > for swap can be locked up within minutes if swap is used intensively. > > The problem is that network block devices do not use mempools like > normal block devices do. As the host cannot control where they receive > packets from, they cannot reliably work out in advance how much memory > they might need. > > Some years ago, Peter Ziljstra developed a series of patches that > supported swap over an NFS that some distributions are carrying in > their kernels. This patch series borrows very heavily from Peter's work > to support swapping over NBD (the relatively straight-forward case) > and uses throttling instead of dynamically resized memory reserves > so the series is not too unwieldy for review. I have to say, I look over these patches and my mind wants to turn to things like puppies. And ice cream. There's quite some complexity added here in areas which are already reliably unreliable and afaik swap-over-NBD is not a thing which a lot of people want to do. I can see that swap-over-NFS would be useful to some people, and the fact that distros are carrying swap-over-NFS patches has weight. Do these patches lead on to swap-over-NFS? If so, how much more additional complexity are we buying into for that? -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>