> From: James Bottomley [mailto:James.Bottomley@xxxxxxxxxxxxxxxxxxxxx] > Subject: Re: [GIT PULL] mm: frontswap (for 3.2 window) > > Actually, I think there's an unexpressed fifth requirement: > > 5. The optimised use case should be for non-paging situations. Not quite sure what you mean here (especially for frontswap)... > The problem here is that almost every data centre person tries very hard > to make sure their systems never tip into the swap zone. A lot of > hosting datacentres use tons of cgroup controllers for this and > deliberately never configure swap which makes transcendent memory > useless to them under the current API. I'm not sure this is fixable, I can't speak for cgroups, but the generic "state-of-the-art" that you describe is a big part of what frontswap DOES try to fix, or at least ameliorate. Tipping "into the swap zone" is currently very bad. Very very bad. Frontswap doesn't "solve" swapping, but it is the foundation for some of the first things in a long time that aren't just "add more RAM." > but it's the reason why a large swathe of users would never be > interested in the patches, because they by design never operate in the > region transcended memory is currently looking to address. It's true, those that are memory-rich and can spend nearly infinite amounts on more RAM (and on high-end platforms that can expand to hold massive amounts of RAM) are not tmem's target audience. > This isn't an inherent design flaw, but it does ask the question "is > your design scope too narrow?" Considering all the hazing that I've gone through to get this far, you think I should _expand_ my design scope?!? :-) Thanks, I guess I'll pass. :-) Dan -- 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