Hi
user
Admin Login:
Username:
Password:
Name:
System Suspend Support in the Linux Kernel 2007 - 2017
--client
lca
--show
lca2018
--room guthrie 13644 --force
Prev: 14 Budget CNC machining
Next: 14 Aussie Add-ons: Liberating Australian catch-up TV with Open Source
show more...
Author(s):
Rafael Wysocki
Location
Guthrie Theatre CB06.03.28
Date
jan Thu 25
Days Raw Files
Start
14:35
First Raw Start
14:09
Duration
0:45:0
Offset
0:25:11
End
15:20
Last Raw End
15:39
Chapters
00:00
0:04:47
0:34:47
Total cuts_time
44 min.
http://lca2018.linux.org.au/schedule/presentation/30/
raw-playlist
raw-mp4-playlist
encoded-files-playlist
host
archive
public
tweet
mp4
svg
png
assets
release.pdf
System_Suspend_Support_in_the_Linux_Kernel_2007_2017.json
logs
Admin:
episode
episode list
cut list
raw files day
marks day
marks day
image_files
State:
---------
borked
edit
encode
push to queue
post
richard
review 1
email
review 2
make public
tweet
to-miror
conf
done
Locked:
clear this to unlock
Locked by:
user/process that locked.
Start:
initially scheduled time from master, adjusted to match reality
Duration:
length in hh:mm:ss
Name:
Video Title (shows in video search results)
Emails:
email(s) of the presenter(s)
Released:
Unknown
Yes
No
has someone authorised pubication
Normalise:
Channelcopy:
m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:
filename.png
Description:
System suspend is relatively straightforward from the user perspective. When requested, it should put the whole system into a state with all activity stopped and reduced power draw. Next, the system should wait in that state for an event to wake it up and then go back to its previous state and get on with whatever it was doing before, ideally without any side-effects visible to the user. The implementation of that in an Operating System, however, turns out to be seriously complicated. First of all, stopping all activity in a multiprocessor system, like a modern laptop, is a rather tricky business and it cannot take too much time, or it will not be appreciated by users. On top of that, in general, all devices in the system need to be put into low-power states, so that the total power draw of the suspended system can be as low as expected and that should happen quickly too. Still, some devices need to remain sufficiently active to be able to wake up the system when needed and that has to be taken into account along with all of the possible dependencies between devices. Moreover, the time it takes for the system to get back to the working state also cannot be too long and, finally, all of the above must be absolutely reliable or system suspend will not be used. Combined, all of these items may look a bit intimidating. Of course, that did not prevent Linux kernel developers from implementing system suspend support, but it took quite some time to reach the current state of the art. Various parts of the suspend infrastructure have been under development for several years, but it started to be recognized as a separate feature in 2007. Overall, a lot of progress has been made and nowadays system suspend in Linux is regarded as one of the features that generally should work. There are gaps in it and occasional regressions happen, but also there is a huge number of Linux-based systems in the field that suspend reliably on a very regular basis. However, it is instructive and somewhat entertaining to look back at where we started and how we have got where we are today. That leads to some interesting observations. One of them, which seems to be particularly important to me, is that improvements are made by iterating three basic steps again and again. First, we get some better understanding of what really happens, either by diagnosing reported issue or by adding support for new technologies. That better understanding results in code improvements which typically unlock some use cases that were not viable previously. Next, the new use cases are exercised and become the source of feedback which then causes our understanding of things to get better still and a new cycle begins. Every iteration takes us to the next level and progress is made this way. That pattern is clearly visible in the history of the development of system suspend support in Linux, but it is not the only thought-provoking aspect of it as I will show in my presentation.
markdown
Comment:
production notes
2018-01-25/14_09_49.ts
Apply:
14:09:49 - 14:25:35 ( 00:15:46 )
S:
14:09:49 -
E:
14:39:48
D:
00:29:59
(
End:
946.0)
show more...
vlc ~/Videos/veyepar/lca/lca2018/dv/guthrie/2018-01-25/14_09_49.ts :start-time=00.0 --audio-desync=0
Raw File
Cut List
14:09:49
seconds: 0.0
Wall: 14:09:49
Duration
00:29:59
14:39:48
seconds: 946.0
Wall: 14:25:35
Comments:
mp4
mp4.m3u
dv.m3u
Split:
Sequence:
:
delete
2018-01-25/14_09_49.ts
Apply:
14:25:35 - 14:35:01 ( 00:09:26 )
S:
14:09:49 -
E:
14:39:48
D:
00:29:59
(
Start:
946.0) (
End:
1512.0)
show more...
vlc ~/Videos/veyepar/lca/lca2018/dv/guthrie/2018-01-25/14_09_49.ts :start-time=0946.0 --audio-desync=0
Raw File
Cut List
14:09:49
seconds: 946.0
Wall: 14:25:35
Duration
00:29:59
14:39:48
seconds: 1512.0
Wall: 14:35:01
Comments:
mp4
mp4.m3u
dv.m3u
Split:
Sequence:
:
delete
2018-01-25/14_09_49.ts
Apply:
14:35:01 - 14:39:48 ( 00:04:47 )
S:
14:09:49 -
E:
14:39:48
D:
00:29:59
(
Start:
1512.0)
show more...
vlc ~/Videos/veyepar/lca/lca2018/dv/guthrie/2018-01-25/14_09_49.ts :start-time=01512.0 --audio-desync=0
Raw File
Cut List
14:09:49
seconds: 1512.0
Wall: 14:35:01
Duration
00:29:59
14:39:48
seconds: 0.0
Wall: 14:09:49
Comments:
mp4
mp4.m3u
dv.m3u
Split:
Sequence:
:
delete
2018-01-25/14_39_49.ts
Apply:
14:39:49 - 15:09:49 ( 00:30:00 )
S:
14:39:49 -
E:
15:09:49
D:
00:30:00
show more...
vlc ~/Videos/veyepar/lca/lca2018/dv/guthrie/2018-01-25/14_39_49.ts :start-time=00.0 --audio-desync=0
Raw File
Cut List
14:39:49
seconds: 0.0
Wall: 14:39:49
Duration
00:30:00
15:09:49
seconds: 0.0
Wall: 14:39:49
Comments:
mp4
mp4.m3u
dv.m3u
Split:
Sequence:
:
delete
2018-01-25/15_09_49.ts
Apply:
15:09:49 - 15:19:50 ( 00:10:01 )
S:
15:09:49 -
E:
15:39:48
D:
00:29:59
(
End:
601.0)
show more...
vlc ~/Videos/veyepar/lca/lca2018/dv/guthrie/2018-01-25/15_09_49.ts :start-time=00.0 --audio-desync=0
Raw File
Cut List
15:09:49
seconds: 0.0
Wall: 15:09:49
Duration
00:29:59
15:39:48
seconds: 601.0
Wall: 15:19:50
Comments:
mp4
mp4.m3u
dv.m3u
Split:
Sequence:
:
delete
2018-01-25/15_09_49.ts
Apply:
15:19:50 - 15:39:48 ( 00:19:58 )
S:
15:09:49 -
E:
15:39:48
D:
00:29:59
(
Start:
601.0)
show more...
vlc ~/Videos/veyepar/lca/lca2018/dv/guthrie/2018-01-25/15_09_49.ts :start-time=0601.0 --audio-desync=0
Raw File
Cut List
15:09:49
seconds: 601.0
Wall: 15:19:50
Duration
00:29:59
15:39:48
seconds: 0.0
Wall: 15:09:49
Comments:
mp4
mp4.m3u
dv.m3u
Split:
Sequence:
:
delete
Rf filename:
root is .../show/dv/location/, example: 2013-03-13/13:13:30.dv
Sequence:
get this:
check and save to add this
2018-01-25/14_09_49.ts
2018-01-25/14_39_49.ts
2018-01-25/15_09_49.ts
Veyepar
Video Eyeball Processor and Review
