)]}' { "log": [ { "commit": "df2e71fb9115a8d4f721fb1464db09adc8332bc5", "tree": "460230de8257235dc57f9835582afb0875cbc057", "parents": [ "be4f1bb2627c2d963d09be1cd69f8820995a9112" ], "author": { "name": "akpm@osdl.org", "email": "akpm@osdl.org", "time": "Mon Jan 09 20:51:37 2006 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Tue Jan 10 08:01:25 2006 -0800" }, "message": "[PATCH] dump_thread() cleanup\n\n\r)\n\nFrom: Adrian Bunk \u003cbunk@stusta.de\u003e\n\n- create one common dump_thread() prototype in kernel.h\n\n- dump_thread() is only used in fs/binfmt_aout.c and can therefore be\n removed on all architectures where CONFIG_BINFMT_AOUT is not\n available\n\nSigned-off-by: Adrian Bunk \u003cbunk@stusta.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "404351e67a9facb475abf1492245374a28d13e90", "tree": "5ef4e78b399b36a46eda339ad0cd27556fc5b9a2", "parents": [ "fc2acab31be8e869b2d5f6de12f557f6f054f19c" ], "author": { "name": "Hugh Dickins", "email": "hugh@veritas.com", "time": "Sat Oct 29 18:16:04 2005 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Sat Oct 29 21:40:38 2005 -0700" }, "message": "[PATCH] mm: mm_init set_mm_counters\n\nHow is anon_rss initialized? In dup_mmap, and by mm_alloc\u0027s memset; but\nthat\u0027s not so good if an mm_counter_t is a special type. And how is rss\ninitialized? By set_mm_counter, all over the place. Come on, we just need to\ninitialize them both at once by set_mm_counter in mm_init (which follows the\nmemcpy when forking).\n\nSigned-off-by: Hugh Dickins \u003chugh@veritas.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "1363c3cd8603a913a27e2995dccbd70d5312d8e6", "tree": "405e7fc1ef44678f3ca0a54c536d0457e6e80f45", "parents": [ "e7c8d5c9955a4d2e88e36b640563f5d6d5aba48a" ], "author": { "name": "Wolfgang Wander", "email": "wwc@rentec.com", "time": "Tue Jun 21 17:14:49 2005 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@ppc970.osdl.org", "time": "Tue Jun 21 18:46:16 2005 -0700" }, "message": "[PATCH] Avoiding mmap fragmentation\n\nIngo recently introduced a great speedup for allocating new mmaps using the\nfree_area_cache pointer which boosts the specweb SSL benchmark by 4-5% and\ncauses huge performance increases in thread creation.\n\nThe downside of this patch is that it does lead to fragmentation in the\nmmap-ed areas (visible via /proc/self/maps), such that some applications\nthat work fine under 2.4 kernels quickly run out of memory on any 2.6\nkernel.\n\nThe problem is twofold:\n\n 1) the free_area_cache is used to continue a search for memory where\n the last search ended. Before the change new areas were always\n searched from the base address on.\n\n So now new small areas are cluttering holes of all sizes\n throughout the whole mmap-able region whereas before small holes\n tended to close holes near the base leaving holes far from the base\n large and available for larger requests.\n\n 2) the free_area_cache also is set to the location of the last\n munmap-ed area so in scenarios where we allocate e.g. five regions of\n 1K each, then free regions 4 2 3 in this order the next request for 1K\n will be placed in the position of the old region 3, whereas before we\n appended it to the still active region 1, placing it at the location\n of the old region 2. Before we had 1 free region of 2K, now we only\n get two free regions of 1K -\u003e fragmentation.\n\nThe patch addresses thes issues by introducing yet another cache descriptor\ncached_hole_size that contains the largest known hole size below the\ncurrent free_area_cache. If a new request comes in the size is compared\nagainst the cached_hole_size and if the request can be filled with a hole\nbelow free_area_cache the search is started from the base instead.\n\nThe results look promising: Whereas 2.6.12-rc4 fragments quickly and my\n(earlier posted) leakme.c test program terminates after 50000+ iterations\nwith 96 distinct and fragmented maps in /proc/self/maps it performs nicely\n(as expected) with thread creation, Ingo\u0027s test_str02 with 20000 threads\nrequires 0.7s system time.\n\nTaking out Ingo\u0027s patch (un-patch available per request) by basically\ndeleting all mentions of free_area_cache from the kernel and starting the\nsearch for new memory always at the respective bases we observe: leakme\nterminates successfully with 11 distinctive hardly fragmented areas in\n/proc/self/maps but thread creating is gringdingly slow: 30+s(!) system\ntime for Ingo\u0027s test_str02 with 20000 threads.\n\nNow - drumroll ;-) the appended patch works fine with leakme: it ends with\nonly 7 distinct areas in /proc/self/maps and also thread creation seems\nsufficiently fast with 0.71s for 20000 threads.\n\nSigned-off-by: Wolfgang Wander \u003cwwc@rentec.com\u003e\nCredit-to: \"Richard Purdie\" \u003crpurdie@rpsys.net\u003e\nSigned-off-by: Ken Chen \u003ckenneth.w.chen@intel.com\u003e\nAcked-by: Ingo Molnar \u003cmingo@elte.hu\u003e (partly)\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2", "tree": "0bba044c4ce775e45a88a51686b5d9f90697ea9d", "parents": [], "author": { "name": "Linus Torvalds", "email": "torvalds@ppc970.osdl.org", "time": "Sat Apr 16 15:20:36 2005 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@ppc970.osdl.org", "time": "Sat Apr 16 15:20:36 2005 -0700" }, "message": "Linux-2.6.12-rc2\n\nInitial git repository build. I\u0027m not bothering with the full history,\neven though we have it. We can create a separate \"historical\" git\narchive of that later if we want to, and in the meantime it\u0027s about\n3.2GB when imported into git - space that would just make the early\ngit days unnecessarily complicated, when we don\u0027t have a lot of good\ninfrastructure for it.\n\nLet it rip!\n" } ] }