| commit | c7283981ec141bf3c261c13f7550bc712c6ed84a | |
| author | Andres Salomon <dilinger@debian.org> | |
| Mon, 3 Nov 2008 01:08:25 +0000 (3 01:08 +0000) | ||
| committer | Mike Westerhof <mwester@dls.net> | |
| Tue, 4 Nov 2008 03:22:58 +0000 (3 21:22 -0600) | ||
| tree | 26916fb2097b1eb31667b425c84f0f64286c1011 | treesnapshot (tar.gz zip) |
| parent | 743ca14a0297ff77890ee541b9cc72e682c5efb1 | commitdiff |
jffs2-choke-gc-thread.patch
I've noticed some pretty poor behavior on OLPC machines after bootup, when
gdm/X are starting. The GCD monopolizes the scheduler (which in turns means
it gets to do more nand i/o), which results in processes taking much much
longer than they should to start.
As an example, on an OLPC machine going from OFW to a usable X (via auto-login
gdm) takes 2m 30s. The majority of this time is consumed by the switch into
graphical mode. With this patch, we cut a full 60s off of bootup time. After
bootup, things are much snappier as well.
Note that we have seen a CRC node error with this patch that causes the machine
to fail to boot, but we've also seen that problem without this patch.
Signed-off-by: Andres Salomon <dilinger@debian.org>
I've noticed some pretty poor behavior on OLPC machines after bootup, when
gdm/X are starting. The GCD monopolizes the scheduler (which in turns means
it gets to do more nand i/o), which results in processes taking much much
longer than they should to start.
As an example, on an OLPC machine going from OFW to a usable X (via auto-login
gdm) takes 2m 30s. The majority of this time is consumed by the switch into
graphical mode. With this patch, we cut a full 60s off of bootup time. After
bootup, things are much snappier as well.
Note that we have seen a CRC node error with this patch that causes the machine
to fail to boot, but we've also seen that problem without this patch.
Signed-off-by: Andres Salomon <dilinger@debian.org>
| fs/jffs2/background.c | diffblobblamehistory |