Back in February
checkpoint/restart patch set was brought to the kernel mailing list with a
request for inclusion in the -mm tree. That was immediately prior to the
2.6.34 merge window, so there were limited amounts of developer attention
available for review. At that time, Andrew Morton suggested
I'd suggest waiting until very shortly after 2.6.34-rc1 then please
send all the patches onto the list and let's get to work.
The checkpoint/restart developers did post the the patches in March, to
relatively little response. Shortly before the
2.6.35 merge window, they reposted the whole thing as a 100-patch series.
Unsurprisingly, there have been some complaints about the massive mailing,
but there is another outcome which is less fortunate: the patches are not
being looked at.
That, too, is unsurprising. The amount of developer time available for
patch review is insufficient in the best of times, and it gets worse as the
merge window approaches. Even the most seasoned reviewer is going to be a
bit intimidated by a 100-patch series which pokes its fingers into almost
every part of the core kernel. Most of them will decide that they have
more important things to do elsewhere.
So, once again, checkpoint/restart is likely to be put on hold until after
the next merge window. After that, if it comes back in more manageable
pieces, the developers might truly get to work.
to post comments)