On Thu, Mar 22, 2012 at 11:56:37AM -0700, Dan Smith wrote: > AA> but now it's time to go back coding and add THP native > AA> migration. That will benefit everyone, from cpuset in userland to > AA> numa/sched. > > I dunno about everyone else, but I think the thing I'd like to see most > (other than more interesting benchmarks) is a broken out and documented > set of patches instead of the monolithic commit you have now. I know you > weren't probably planning to do that until numasched came along, but it > sure would help me digest the differences in the two approaches. I uploaded AutoNUMA public to my git tree autonuma branch, the day before numa/sched was posted to allow people to start testing it. I didn't announce it yet because I wasn't sure if it was worth posting it until I had the time to split the patches. Then I changed my mind and posted it as the monolith that it was. I think I'll try to attack the THP native migration, if it looks like it takes more than one or two days to do it, I'll abort it and do the patch-splitting/cleanup/documentation work first so you can review review the code better ASAP. The advantage of doing it sooner is, it gets more of the testing that is going on right now from you and everyone else, plus I dislike leaving that important feature missing while many benchmarks are being run, as it's going to certainly be measurable when the workload changes massively and lots of hugepages are moved around by knuma_migrated. Boosting khugepaged tends to hide it for now though (as shown by specjbb). Thanks, Andrea -- 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>