Forgot your password?
Open Source Operating Systems Upgrades Linux

Linux 3.15 Will Suspend & Resume Much Faster 117

Posted by Soulskill
from the cutting-into-my-foot-tapping-time dept.
An anonymous reader writes "The Linux 3.15 kernel now in its early life will be able to suspend and resume much faster than previous versions of the Linux kernel. A few days ago we saw ACPI and Power Management updates that enable asynchronous threads for more suspend and resume callbacks. Carrying out more async operations leads to reduced time for the system suspend and then resuming. According to one developer, it was about an 80% time savings within one of the phases. On Friday, work was merged that ensured the kernel is no longer blocked by waiting for ATA devices to resume. Multiple ATA devices can be woken up simultaneously, and any ATA commands for the device(s) will be queued until they have powered up. According to an blog post on the ATA/SCSI resume optimization patches, when tested on three Intel Linux systems the resume time was between 7x and 12x faster (not including the latest ACPI/PM S&R optimizations)."
This discussion has been archived. No new comments can be posted.

Linux 3.15 Will Suspend & Resume Much Faster

Comments Filter:
  • Re:Caution (Score:5, Informative)

    by SpankiMonki (3493987) on Saturday April 12, 2014 @05:26PM (#46735859)

    There's a reason why RAID controllers tend to wake up drives sequentially.

    And the RAID controllers will continue to do just that. All this change does is allow the kernel to continue resuming without having to wait for the device to report that it's ready. Any commands sent to the device in the meantime are queued.

  • Re:Caution (Score:3, Informative)

    by Anonymous Coward on Saturday April 12, 2014 @05:52PM (#46736023)

    Consider that Linux runs on everything. It's not unlikely that there are plenty of clusters out there that suspends whole computers when the power is not needed. If they are also filled with HDDs, then that use case arises.

    I think it's a valid point, even though it's not very common.

  • Re:Caution (Score:2, Informative)

    by Anonymous Coward on Saturday April 12, 2014 @06:10PM (#46736143)
    If it's a hardware RAID controller then the kernel should "see" a single logical device it needs to wake up, and it can leave it to the controller firmware to wake up the drives in the correct order.
  • by evilviper (135110) on Saturday April 12, 2014 @06:35PM (#46736257) Journal

    The third big software factor is the BIOS. "coreboot", formerly "LinuxBIOS", is blazingly fast compared to most proprietary BIOS's. It has made some inroads but is still not available for any commercial systems I can find. So no matter what is done in the other two factors, the BIOS is still a limiting factor of suspend and restore delays.

    POST has to be performed by the BIOS when restoring from hibernation, but NOT suspend. So no, the BIOS is NOT a significant "limiting factor of suspend and [resume]" operations.

  • by Anonymous Coward on Saturday April 12, 2014 @06:36PM (#46736265)
    That's too slow... osx takes a second or so. And the newest windows is trying to copy osx resume speed. Perhaps now, linux is copying windows resume.
  • WTF slashdot (Score:2, Informative)

    by Anonymous Coward on Saturday April 12, 2014 @09:45PM (#46737351)

    I'm in beta and I click classic which is on top it gets me to classic, hit the comments link and brings me back to beta and this is in a fucking loop. Stupid assholes, a website should be about the content itself not the bullshit eye candy which is taking space anyway. FUCKING RETARDS!!!

  • Re:WTF slashdot (Score:4, Informative)

    by Janek Kozicki (722688) on Sunday April 13, 2014 @05:04AM (#46738807) Journal
    Just go to a new and better site: []

Are we running light with overbyte?