X-Git-Url: https://git.decadent.org.uk/gitweb/?p=kernel-news-talk.git;a=blobdiff_plain;f=index.html;h=12c844c561d94da49c17153299ec0870902c0eb0;hp=600c133ce925a726eacf4c44504aa3158f1da115;hb=c8edb32ab191e7e9e3cab0174437a51c680de859;hpb=12e66dc4c6d3634826738cbfd27686174606f404 diff --git a/index.html b/index.html index 600c133..12c844c 100644 --- a/index.html +++ b/index.html @@ -4,7 +4,7 @@ -What's new in the Linux kernel - DebConf 2013 +What's new in the Linux kernel - DebConf 2014 @@ -39,7 +39,7 @@ @@ -50,6 +50,7 @@

What's new in the Linux kernel

+

and what's missing in Debian

Ben Hutchings

@@ -58,24 +59,297 @@ + + +
+

Linux releases early and often

+ +
+ +
+

Recap of last year's features (1)

+ +
+ +
+

Recap of last year's features (2)

+ +
+ +
+

Unnamed temporary files [3.11]

+ +
+ +
+

Lustre filesystem [3.12]

+ +
+ +
+

Network busy-polling [3.11] (1)

+

A conventional network request/response process looks like:

+ +
    +
  1. + Task calls send(); network stack constructs a + packet; driver adds it to hardware Tx queue +
  2. +
  3. + Task calls poll() or recv(), which blocks; + kernel puts it to sleep and possibly idles the CPU +
  4. +
  5. + Network adapter receives response and generates IRQ, waking + up CPU +
  6. +
  7. + Driver's IRQ handler schedules polling of the hardware Rx + queue (NAPI) +
  8. +
  9. + Kernel runs the driver's NAPI poll function, which passes + the response packet into the network stack +
  10. +
  11. + Network stack decodes packet headers and adds packet to + the task's socket +
  12. +
  13. + Network stack wakes up sleeping task; scheduler switches + to it and the socket call returns +
  14. +
+
+
+ +
+

Network busy-polling [3.11] (2)

+ +
+ +
+

Btrfs offline dedupe [3.12]

+ +
+ +
+

nftables [3.13]

+ +
+ +
+

User-space lockdep [3.14]

+ +
+ +
+

arm64 and ppc64el ports

+