-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/18/2014 03:19 PM, Andrew Morton wrote: > On Mon, 17 Nov 2014 21:41:57 -0500 Rik van Riel <riel@xxxxxxxxxx> > wrote: > >> That way people can understand what the code does simply by >> looking at the changelog - no need to go find old linux-kernel >> mailing list threads. > > Yes please, there's a ton of stuff here which we should attempt to > capture. > > https://lkml.org/lkml/2012/8/15/765 is useful. > > I'm assuming that with the "foo < 5" hack, an application which > forked 5 times then did a lot of work would still trigger the > "catastrophic issue at page reclaim time" issue which Rik > identified at https://lkml.org/lkml/2012/8/20/265? It's not "forking 5 times", it is "forking >>5 generations deep". There are a few programs that do that, but it does not appear that they are forking servers like apache or sendmail (which fork from the 2nd generation, and then sometimes again to exec a helper from the 4th generation). > There are real-world workloads which are triggering this slab > growth problem, yes? (Detail them in the changelog, please). There are, but the overlap between "forks >>5 generations deep" and "forks a bajillion child processes" appears to be zero. - -- All rights reversed -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJUbATgAAoJEM553pKExN6Ds84H/ixCr4Q5C09sDISuw9y/PsVI moXPbqgefpzbS316MgD1AMl7rj2OWAMiQcRGQ6yMelXOyuB89XTiBi19t5UxaSUn tuFnxeknoIL0155yTfszETRGjN9mUKoyk9HAhND1T+x2VFLwaQYyk7CdZC/h7IQ7 m1jfwlR30r0Ie6x5lkN1XaculdWdXjr7wTwUWeOVsc6lWv3kR3dC52LKsB4fv340 gBeL5sTDNNp6r5Gfr5QL7fQR0eLVvhStSmsm4GbggpVSBSCpZ++h8eTjdtHxuJO3 jtgEGAvhnLDSqRi6NG6dKoxtXW8++hnFIKBw1Ec36NTuTkbKiHo9EQujINtXWro= =/EU5 -----END PGP SIGNATURE----- -- 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/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>