Bootloader-Based S2D(suspend to disk) Mechanism on mobile
summary
Claims a bootloader-side S2D restore that loads snapshot in blocks rather than page-by-page, bypasses the temporary kernel and thus avoids temporary kernel probing overhead. A prototype implements block-based restore from swap-format snapshots and measures the kernel-based flow spending ~3s for the temp kernel plus ~20s for page-by-page restore versus a bootloader prototype doing the uncompressed restore in ~0.2–0.8s; an Android device test shows end-to-end resume around 8s. prototype uncompressed snapshot
AI-written summary · about
chapters (11)
- 0:00Introduction to S2D
- 1:04Bootloader-based S2D proposal
- 2:56Suspend and restore processes
- 5:07Kernel-based S2D details
- 6:10Bootloader vs kernel S2D comparison
- 8:45Compression impact on restore time
- 9:31Data page storage methods
- 11:41Android mobile device experiment
- 12:48Kernel and bootloader dependency
- 14:14Compression timing benefits
- 15:20Q&A summary
related talks
48mExtending the swsusp Hibernation Framework to ARM
34mTweaking the Linux Boot Flow for an Accelerated ADAS Experience
24mSoftware Optimization for Early Linux Boot for Time Critical...
48mUnified Boot Time Measurement: A Precise, Scalable Framework for Multi-Processor Systems
39m“Early Boot and Late Attach” of Remote Processor...
39mTiming Boot Time Reduction Techniques
38mDeferred Memblocks Init for Boot Time Reduction
41mBoot-Time BOF