<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2-ppt DokuWiki" -->
<?xml-stylesheet href="http://wiki.linuxplumbersconf.org/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="http://wiki.linuxplumbersconf.org/feed.php">
        <title>Linux Plumbers Conf Wiki</title>
        <description></description>
        <link>http://wiki.linuxplumbersconf.org/</link>
        <image rdf:resource="http://wiki.linuxplumbersconf.org/lib/images/favicon.ico" />
       <dc:date>2021-12-07T17:26:36+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://wiki.linuxplumbersconf.org/2017:device_tree?rev=1509007402&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.linuxplumbersconf.org/2017:linux-kernel_memory_model_workshop?rev=1508246681&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.linuxplumbersconf.org/2017:md_raid_general_discussion?rev=1505282112&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.linuxplumbersconf.org/2017:vfio_iommu_pci?rev=1505262639&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.linuxplumbersconf.org/2017:power_management_and_energy-awareness?rev=1505024041&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.linuxplumbersconf.org/2017:tracing?rev=1505023910&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.linuxplumbersconf.org/2017:topics?rev=1504597957&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="http://wiki.linuxplumbersconf.org/lib/images/favicon.ico">
        <title>Linux Plumbers Conf Wiki</title>
        <link>http://wiki.linuxplumbersconf.org/</link>
        <url>http://wiki.linuxplumbersconf.org/lib/images/favicon.ico</url>
    </image>
    <item rdf:about="http://wiki.linuxplumbersconf.org/2017:device_tree?rev=1509007402&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-10-26T08:43:22+00:00</dc:date>
        <title>2017:device_tree</title>
        <link>http://wiki.linuxplumbersconf.org/2017:device_tree?rev=1509007402&amp;do=diff</link>
        <description>STATUS: A Devicetree Workshop will be held in conjunction with Kernel Summit in Prague. The Devicetree workshop will be held Thursday afternoon, 26 October 2017. This page is being used to organise the workshop agenda

There will not be a Devicetree miniconference at Linux Plumbers Conference this year.</description>
    </item>
    <item rdf:about="http://wiki.linuxplumbersconf.org/2017:linux-kernel_memory_model_workshop?rev=1508246681&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-10-17T13:24:41+00:00</dc:date>
        <title>2017:linux-kernel_memory_model_workshop - Update ocaml version</title>
        <link>http://wiki.linuxplumbersconf.org/2017:linux-kernel_memory_model_workshop?rev=1508246681&amp;do=diff</link>
        <description>Why frighten small children by reading memory-barriers.txt to them when you can now automate this process with a shiny new tool allegedly implementing the Linux-kernel memory model?  This tool takes a “litmus test” that contains concurrent quasi-C code along with an assertion.  The tool then tells you whether this assertion always, sometimes, or never triggers after the concurrent quasi-C code completes execution.</description>
    </item>
    <item rdf:about="http://wiki.linuxplumbersconf.org/2017:md_raid_general_discussion?rev=1505282112&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-09-13T05:55:12+00:00</dc:date>
        <title>2017:md_raid_general_discussion</title>
        <link>http://wiki.linuxplumbersconf.org/2017:md_raid_general_discussion?rev=1505282112&amp;do=diff</link>
        <description>A micro conference proposal for general MD raid discussion.

Why people should be here

In the last years, we have many development activities in md raid, e.g.

	*  Raid5 cache
		*  This is an effort to close raid5 writing hole (data lost when system crash happens), the original idea was from Ext4 file system journal (this is why its earlier name was raid5-journal). Now raid5 cache can be used to improve performance for writing burst and improve tolerance of writing hole.</description>
    </item>
    <item rdf:about="http://wiki.linuxplumbersconf.org/2017:vfio_iommu_pci?rev=1505262639&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-09-13T00:30:39+00:00</dc:date>
        <title>2017:vfio_iommu_pci</title>
        <link>http://wiki.linuxplumbersconf.org/2017:vfio_iommu_pci?rev=1505262639&amp;do=diff</link>
        <description>The introduction of system technologies that improve devices capabilities and
performance (eg PCI ATS (Address Translation Service)/PRI(Page Request
Interface), enabling Shared Virtual Memory (SVM) between devices and CPUs) is
making PCI devices, the system IOMMUs they are connected to and the VFIO layer
used to managed them (for userspace and device passthrough) more and more
tightly coupled, with related kernel interfaces that have to be designed
in-sync for all three subsystems.</description>
    </item>
    <item rdf:about="http://wiki.linuxplumbersconf.org/2017:power_management_and_energy-awareness?rev=1505024041&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-09-10T06:14:01+00:00</dc:date>
        <title>2017:power_management_and_energy-awareness</title>
        <link>http://wiki.linuxplumbersconf.org/2017:power_management_and_energy-awareness?rev=1505024041&amp;do=diff</link>
        <description>The Linux Plumbers 2017 Power Management and Energy-awareness track focuses on topics related to power management frameworks, task scheduling in relation to power/energy optimization, and platform power management mechanisms. The goal is to facilitate cross framework and cross platform discussions that can help improve power and energy-awareness in Linux.</description>
    </item>
    <item rdf:about="http://wiki.linuxplumbersconf.org/2017:tracing?rev=1505023910&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-09-10T06:11:50+00:00</dc:date>
        <title>2017:tracing</title>
        <link>http://wiki.linuxplumbersconf.org/2017:tracing?rev=1505023910&amp;do=diff</link>
        <description>The Linux Plumbers 2017 Tracing track is focusing on the various tracing infrastructures in Linux today and how various people and companies use them.

Topic suggestions

	*  Building your own tools around existing kernel infrastructure
	*  Wishlist items for kernel tracing
	*  Issues that have been discovered using tracing
	*  New features in bpf/perf/ftrace
	*  Visualization frameworks
	*  Distributed tracing
	*  Always-on analytics and monitoring (including TCP/networking/storage)
	*  Tracing…</description>
    </item>
    <item rdf:about="http://wiki.linuxplumbersconf.org/2017:topics?rev=1504597957&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-09-05T07:52:37+00:00</dc:date>
        <title>2017:topics</title>
        <link>http://wiki.linuxplumbersconf.org/2017:topics?rev=1504597957&amp;do=diff</link>
        <description>Microconference Tracks for the 2017 Linux Plumbers Conference


This is a list of “microconferences”, which are working sessions which are designed to solve problems in the “plumbing” of Linux – kernel subsystems, core libraries, windowing system, etc. For more information, please see this description on the LPC web page,  What is Linux Plumbing.</description>
    </item>
</rdf:RDF>
