Sexy world of Linux kernel pvops
•
0 likes•7,901 views
The document discusses paravirtualized operations (pv-ops) in the Linux kernel which allows it to detect if it is running under virtualization like Xen or KVM and use optimized operations. Pv-ops was successful and mainly involved bug fixes recently. Most Xen kernel development is in subsystems and amounts to over 50,000 lines of code added per release. Future work includes optimizations to blkback and netback drivers to improve I/O performance, as well as adding perf support and developing a hybrid PV/HVM domain 0 capability. The presenter takes questions at the end.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Sexy world of Linux kernel pvops
Similar to Sexy world of Linux kernel pvops (20)
More from The Linux Foundation
More from The Linux Foundation (20)
Recently uploaded
Recently uploaded (20)
Sexy world of Linux kernel pvops
- 1. Sexy world of Linux kernel pvops project by Konrad Rzeszutek Wilk
- 3. Agenda ● Quick introduction [5 min] ● Past ● Present ● Future ● Surprises ● QA
- 4. Paravirtualized Operations (pv-ops) ● Solves the early problem of classic Xen kernels: a distribution needed to ship two kernels: one for native, one for Xen. ● Pvops extensions solved the problem - it allows the Linux kernel during runtime to figure out if it is running under any virtualization stacks (Xen, KVM) and swap over to using optimized low-level operations for the specific virtualization stack.
- 5. Pvops success ● Its been quite successful - and since its introduction has not had much changes. Lately it has been more of removing some of them as they are not used. ● Majority of Xen-related Linux kernel development is in (next slide)
- 8. Development by lines of code
- 9. What went in v3.X? http://wiki.xen.org/wiki/XenParavirtOps#Changelog ● v3.6: MCE, pcpu, perf fixes, and bug fixes ● v3.5: perf enablement, bug fixes, perf works ● v3.4: ACPI PM work, PV console in HVM, blkback can work in HVM domain ● v3.3: TTM works with Xen, faster IRQ ACK, bug-fixes, netback can work in HVM domain ● v3.2: blkback supporting 'feature-discard', sync wall clock to hypervisor,..
- 10. Fast pace of Linux kernel ● Every 2-3 months released! ● Exciting new features ● No stale code! ● Must have code tested two weeks before merge window opens ● Maintainers dream - can concentrate on new features without having to worry about backporting in an distro's kernel.
- 11. Surprises! (or not so happy conversations) ● MCE [https://lkml.org/lkml/2012/4/23/286]: "..Because, if you'd hooked into it, just imagine one fine day, when we remove mcelog support, what screaming the xen people will be doing when mcelog doesn't work anymore." ● Followed MCE maintainers desires ● People have misconceptions and sometimes need to explain .. a couple of times. ● We have a responsibility to the general Linux community to help with non-Xen
- 12. Future! http://wiki.xen. org/wiki/Xen_Development_Projects ● Existing patchsets that apply but are not upstream yet: ○ EFI (only for 3.0) ○ kexec ○ microcode ○ oprofile ○ ACPI S3 ○ pv usb ○ pv scsi
- 13. Future - new work! ● blkback faster ○ persistent grants, larger ring, larger segment ○ DIF/DIX ● netback faster ○ persistent grants ○ separate TX/RX rings, large rings ○ separate events, pagepool ○ inline small SKB on ring ● Hybrid PV aka HVM dom0 ● perf ○ sampling the hypervisor ○ sampling the guest
- 14. And more future work... ● pv and pvhvm ticketlocks ● other work as it comes from perf analysis. ● .. detailed list on the URL
- 15. QA