DOCSLIB.ORG

Dell Presentation Template Standard 4:3 Layout

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Dell Presentation Template Standard 4:3 Layout Network Device Naming Matt Domsch Technology Strategist, Office of the CTO Office of the CTO Which is eth0? 2 Office of the CTO Inspiration: Network Switches Ports labeled with slot and port (4/2). Config tools use this label. 3 Office of the CTO Chassis Labels 4 Office of the CTO Problem: Enumeration != Naming • System Administers expect that names are deterministic. Enumeration is non-deterministic. – Racing modprobes (hack: serialized by udev in RHEL6) – Racing firmware loading – Racing udev renames (fixed Sept’09) – PCI depth-first discovery varies based on motherboard layout • Undefined relationship between chassis label and kernel name • Only one name for each device allowed 5 Office of the CTO Current Solutions^WHacks • ifcfg-eth0 and 70-persistent-net.rules – introduces state to stateless systems • pci=bfsort – Whitelists, assumes PCI bus topology is meaningful • Force sane PCI Bus layout – Breadth-first vs. depth-first list – PCI Express is switched, not a bus hierarchy anymore • PXELINUX + ks=bootif – Only works for 1 NIC, and only if you use PXE We need a better solution. 6 Office of the CTO Standards! • HP added NIC ordering information to SMBIOS vendor fields – Displayed by dmidecode, but not otherwise used • Dell added labels to device objects in SMBIOS 2.6 standard – PowerEdge 10G, 11G implement this • Dell proposed labels and index in ACPI _DSM in PCI Firmware Great, so now we have PCI device to BIOS label mappings. Let’s use them! 7 Office of the CTO Idea #1: Rename devices 8 Office of the CTO Code #1: biosdevname & udev rules • Biosdevname written • Udev rules call biosdevname • Distros didn’t like it – “not upstream enough” • Didn’t solve all the problems – USB network devices – Systems w/o BIOS information – Names limited to 15 characters – Still only 1 “correct” name for each device 9 Office of the CTO Shootdown #1: 10 Office of the CTO Idea #2: /dev/netdev/eth0 11 Office of the CTO Shootdown #2: 12 Office of the CTO Idea #3: Punt to the OS Installers! 13 Office of the CTO Proposal #3: Installer Screen ---------- Network Configuration ------------------------ Default [ ] | SMBIOS Names [x] | Driver Names [] | MAC Names [] ----------------------------------------------------------------------- eth0 | Addin_NIC_1 | ice0 | ----------------------------------------------------------------------- eth1 | Embedded_NIC_1 | bce0 | ----------------------------------------------------------------------- eth2 | Embedded_NIC_2 | bce1 | ----------------------------------------------------------------------- eth3 | Embedded_NIC_3 | bce2 | ----------------------------------------------------------------------- eth4 | Embedded_NIC_4 | bce3 | ----------------------------------------------------------------------- ------------ | Next | ------------ 14 Office of the CTO Shootdown #3: 15 Office of the CTO Idea #4: libnetdevname • Export names from BIOS into sysfs – SMBIOS 2.6 standard method, or HP vendor method (patch in linux-next) – PCI SIG Firmware Working Group ECN, ACPI _DSM (pending) • Userspace library maps BIOS name to kernel name extern int netdev_kernelname_to_alias (char *, struct alias **); extern int netdev_alias_to_kernelname (char *, char *); • All userspace programs that handle network names need to be patched to call libnetdevname – ethtool, iproute2, net-tools patches written – NetworkManager, distro installers still needed # ifconfig “Embedded NIC 1” # ethtool –p “Embedded NIC 2” 16 Office of the CTO libnetdevname futures • Handle add-in PCI cards • Additional names “by function” – “public”, “dmz”, “storage”, “backup”, “admin”, … • Methods to get names from other sources • Handle non-PCI devices • Add method to show which NIC is the “boot device” http://linux.dell.com/wiki/index.php/Oss/libnetdevname [email protected] [email protected] 17 Office of the CTO Call to Action • Got a better idea? Suggest it! • BIOS authors: add ACPI _DSM with labels • Kernel: accept our patches to expose names from BIOS (in linux-next on 7/30) • Network tools authors: incorporate libnetdevname • OS installers: incorporate libnetdevname • Network GUI tools (NetworkManager): display all available names for each interface somehow. 18 Office of the CTO Thanks • Greg Kroah-Hartman • Marco d'Itri • Alex Chiang • David Miller • Bryan Kadzban • Bjorn Helgaas • Alan Cox • Scott James Remnant • Neil Horman • Stephen Hemminger • Dan Williams • Thomas Cantwell • Kay Sievers • John Linville • Chip Webb • Narendra K • Sujit K M • Mukund Khatri • Jordan Hargrave • David Zeuthen • Charles Rose • Peter Jones • Bill Fink • Richard Chan • Jon Masters • Rob Townley • Vijay Nijhawan • Bill Nottingham • Kurt Van Dijck • Vinod Kutty • Ben Hutchings • Hannes Reinecke • Jesse Barnes • Dann Frazier • Karl O. Pinc 19 Office of the CTO .
Load more

Recommended publications
  • Communicating Between the Kernel and User-Space in Linux Using Netlink Sockets
    SOFTWARE—PRACTICE AND EXPERIENCE Softw. Pract. Exper. 2010; 00:1–7 Prepared using speauth.cls [Version: 2002/09/23 v2.2] Communicating between the kernel and user-space in Linux using Netlink sockets Pablo Neira Ayuso∗,∗1, Rafael M. Gasca1 and Laurent Lefevre2 1 QUIVIR Research Group, Departament of Computer Languages and Systems, University of Seville, Spain. 2 RESO/LIP team, INRIA, University of Lyon, France. SUMMARY When developing Linux kernel features, it is a good practise to expose the necessary details to user-space to enable extensibility. This allows the development of new features and sophisticated configurations from user-space. Commonly, software developers have to face the task of looking for a good way to communicate between kernel and user-space in Linux. This tutorial introduces you to Netlink sockets, a flexible and extensible messaging system that provides communication between kernel and user-space. In this tutorial, we provide fundamental guidelines for practitioners who wish to develop Netlink-based interfaces. key words: kernel interfaces, netlink, linux 1. INTRODUCTION Portable open-source operating systems like Linux [1] provide a good environment to develop applications for the real-world since they can be used in very different platforms: from very small embedded devices, like smartphones and PDAs, to standalone computers and large scale clusters. Moreover, the availability of the source code also allows its study and modification, this renders Linux useful for both the industry and the academia. The core of Linux, like many modern operating systems, follows a monolithic † design for performance reasons. The main bricks that compose the operating system are implemented ∗Correspondence to: Pablo Neira Ayuso, ETS Ingenieria Informatica, Department of Computer Languages and Systems.
    [Show full text]
  • Linux Kernel and Driver Development Training Slides
    Linux Kernel and Driver Development Training Linux Kernel and Driver Development Training © Copyright 2004-2021, Bootlin. Creative Commons BY-SA 3.0 license. Latest update: October 9, 2021. Document updates and sources: https://bootlin.com/doc/training/linux-kernel Corrections, suggestions, contributions and translations are welcome! embedded Linux and kernel engineering Send them to [email protected] - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 1/470 Rights to copy © Copyright 2004-2021, Bootlin License: Creative Commons Attribution - Share Alike 3.0 https://creativecommons.org/licenses/by-sa/3.0/legalcode You are free: I to copy, distribute, display, and perform the work I to make derivative works I to make commercial use of the work Under the following conditions: I Attribution. You must give the original author credit. I Share Alike. If you alter, transform, or build upon this work, you may distribute the resulting work only under a license identical to this one. I For any reuse or distribution, you must make clear to others the license terms of this work. I Any of these conditions can be waived if you get permission from the copyright holder. Your fair use and other rights are in no way affected by the above. Document sources: https://github.com/bootlin/training-materials/ - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 2/470 Hyperlinks in the document There are many hyperlinks in the document I Regular hyperlinks: https://kernel.org/ I Kernel documentation links: dev-tools/kasan I Links to kernel source files and directories: drivers/input/ include/linux/fb.h I Links to the declarations, definitions and instances of kernel symbols (functions, types, data, structures): platform_get_irq() GFP_KERNEL struct file_operations - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 3/470 Company at a glance I Engineering company created in 2004, named ”Free Electrons” until Feb.
    [Show full text]
  • Linux 2.5 Kernel Developers Summit
    conference reports This issue’s reports are on the Linux 2.5 Linux 2.5 Kernel Developers Linux development, but I certainly Kernel Developers Summit Summit thought that, in all of this time, someone would have brought this group together OUR THANKS TO THE SUMMARIZER: SAN JOSE, CALIFORNIA before. Rik Farrow, with thanks to La Monte MARCH 30-31, 2001 Yarroll and Chris Mason for sharing their Summarized by Rik Farrow Another difference appeared when the notes. first session started on Friday morning. The purpose of this workshop was to The conference room was set up with cir- provide a forum for discussion of cular tables, each with power strips for changes to be made in the 2.5 release of For additional information on the Linux laptops, and only a few attendees were Linux (a trademark of Linus Torvalds). I not using a laptop. USENIX had pro- 2.5 Kernel Developers Summit, see the assume that many people reading this vided Aeronet wireless setup via the following sites: will be familiar with Linux, and I will hotel’s T1 link, and people were busy <http://lwn.net/2001/features/KernelSummit/> attempt to explain things that might be typing and compiling. Chris Mason of unfamiliar to others. That said, the odd- <http://cgi.zdnet.com/slink?91362:12284618> OSDN noticed that Dave Miller had numbered releases, like 2.3 and now 2.5, <http://www.osdn.com/conferences/kernel/> written a utility to modulate the speed of are development releases where the the CPU fans based upon the tempera- intent is to try out new features or make ture reading from his motherboard.
    [Show full text]
  • Linux Kernel 8.1 Introduction
    Page 1 of 6 Linux Kernel 8.1 Introduction: The Linux kernel is a Unix-like operating system kernel used by a variety of operating systems based on it, which are usually in the form of Linux distributions. The Linux kernel is a prominent example of free and open source software. The Linux kernel is released under the GNU General Public License version 2 (GPLv2) (plus some firmware images with various non-free licenses), and is developed by contributors worldwide. Day-to-day development discussions take place on the Linux kernel mailing list. The Linux kernel was initially conceived and created in 1991 by Finnish computer science student Linus Torvalds. Linux rapidly accumulated developers and users who adapted code from other free software projects for use with the new operating system. The Linux kernel has received contributions from thousands of programmers. 8.2 History: History In April 1991, Linus Torvalds, a 21-year-old student at the University of Helsinki, Finland started working on some simple ideas for an operating system. He started with a task switcher in Intel 80386 assembly language and a terminal driver. On 25 August 1991, Torvalds posted the following to comp.os.minix, a newsgroup on Usenet: I'm doing a (free) operating system (just a hobby, won't be big and professional like gnu) for 386(486) AT clones. This has been brewing since April, and is starting to get ready. I'd like any feedback on things people like/dislike in minix, as my OS resembles it somewhat (same physical layout of the file-system (due to practical reasons) among other things).
    [Show full text]
  • Community Notebook Kernel News Zack’S Kernel News
    Community Notebook Kernel News Zack’s Kernel News Chronicler Zack Licensing Confusion performing source distribution, a complete An interesting little licensing escapade occurred machine-readable copy of the corresponding Brown reports on recently. Matthew Garrett noticed that CloudLi- source code, to be distributed under the the latest news, nux corporation had released their lve kernel terms of Sections 1 and 2 above on a medium driver under a new, proprietary license, whereas customarily used for software interchange.” views, dilemmas, before, it had been released under the GPL. So apparently, a written offer would be good Technically, nothing too fishy is going on here enough, and the three-week delay might be and developments because the original author of GPL’d code is still legally acceptable. within the Linux free to release that code under other licenses. But Matthew noticed that, in this particular Kernel Development kernel community. case, the driver still pretended to the kernel to Overflow be a GPL’d driver and still used kernel symbols Thomas Gleixner posed an interesting ques- By Zack Brown that were restricted to GPL-only code. tion – all the more interesting in that it was That’s a big no-no, and Matthew submitted taken so seriously. He pointed out that inter- a patch to make the kernel automatically treat est in the kernel was continuing to grow and the lve module as non-GPL, whether it said it that the number of patch submissions from was or not. But that wasn’t the end of the story individuals and corporations was growing as because licensing is a very touchy legal sub- well.
    [Show full text]
  • Q8:BËJ B<IE<C E<NJ
    GIF>I8DD@E> Kernel News Q8:BËJB<IE<CE<NJ KiXZb`e^B\ie\c ;lZb8e[:fm\i ?Xi[nXi\:fdgXk`Y`c`kp :feki`Ylk`fej Matt Mackall was a bit shaken to discover Adam Osuchowski was poking around in Wang Chen created a web page for kernel a kernel error message that began “Trea- the deep dark places of the kernel and contribution stats. The page breaks down son uncloaked!” The message went on to came upon some hard-coded assembly information by person and employer, as say that the TCP code had detected a bro- that used the xadd instruction. Because well as by change sets and number of ken peer. Matt thought the message was the 386 CPU didn’t implement an xadd lines of code affected. Also, it's possible alarming, so he posted a patch to change instruction, Adam asked whether Linux to search for a given person or employer it. Herbert Xu’s reply was, “What’s next, still supported the 386. The xadd in- and see a graph of only their contribu- you’re going to remove ‘printer on fire’ as struction turned out to be just a bug, but tions. According to Wang’s stats, for ex- well? This message has been there for the incident sparked a discussion about ample, Yahoo employees have contri- eons and is part of Linux lore.” But Alan which older systems were and were not buted much more to version 2.6.25 than Cox said, “It was changed. The printer on supported under Linux.
    [Show full text]
  • Fall 2020 Vol
    ;login FALL 2020 VOL. 45, NO. 3 : & Guide to the Performance of Optane DRAM Jian Yang, Juno Kim, Morteza Hoseinzadeh, Joseph Izraelevitz, and Steven Swanson & Understanding Linux Superpages Weixi Zhu, Alan L. Cox, and Scott Rixner & Interview with Ion Stoica about Serverless Computing Rik Farrow & Measuring the Health of Open Source Projects Georg J.P. Link & Using OpenTrace to Track DB Performance Problems Anatoly Mikhaylov Columns SRE and Justice Laura Nolan Socially Distant Projects Cory Lueninghoener Communicating with BPF Dave Josephsen Hand-Over-Hand Locking for Highly Concurrent Collections Terence Kelly Everything Is a Punch Card Simson L. Garfinkel Thanks to our USENIX Supporters! USENIX appreciates the financial assistance our Supporters provide to subsidize our day-to-day operations and to continue our non-profit mission. Our supporters help ensure: • Free and open access to technical information • Student Grants and Diversity Grants to participate in USENIX conferences • The nexus between academic research and industry practice • Diversity and representation in the technical workplace We need you now more than ever! Contact us at [email protected]. USENIX PATRONS USENIX BENEFACTORS We offer our heartfelt appreciation to the following sponsors and champions of conference diversity, open access, and our SREcon communities via their sponsorship of multiple conferences: Ethyca Dropbox Microsoft Azure Packet Datadog Goldman Sachs LinkedIn Salesforce More information at www.usenix.org/supporters FALL 2020 VOL. 45, NO. 3 EDITOR EDITORIAL Rik Farrow 2 Musings Rik Farrow MANAGING EDITOR Michele Nelson SYSTEMS COPY EDITORS 6 An Empirical Guide to the Behavior and Use of Scalable Steve Gilmartin Persistent Memory Jian Yang, Juno Kim, Morteza Hoseinzadeh, Amber Ankerholz Joseph Izraelevitz, and Steven Swanson PRODUCTION 12 How to Not Copy Files Yang Zhan, Alex Conway, Nirjhar Mukherjee, Arnold Gatilao Ian Groombridge, Martín Farach-Colton, Rob Johnson, Yizheng Jiao, Ann Heron Michael A.
    [Show full text]
  • Intel & Freebsd
    Intel & FreeBSD: Better Together Ben Widawsky <[email protected]> Agenda ● Introduction (OTC & Me) ● Intel’s past involvement with BSD ● Intel’s latest involvement with BSD ● What’s next ● Power Management deep-dive ● Q&A Ben Widawsky ● Introduced to FreeBSD 5.0 in 2003 by kensmith@ ● Software Developer at Intel since 2005 ● Focus switched to FreeBSD upstream work in 2018 ● Diverse career Intel Open Source Technology Center (OTC) ● Organization specializing in Open Source ● 20 years building expertise and acquiring industry talent ○ The other Alan Cox ● Contributes to over 100 community projects ● Community Friendly licensing ○ Match the ecosystem when possible ■ GPLv2 or GPLv3 for utilities close to Linux Kernel ■ Apache for cloud BSD-Friendly Case Studies Intel Linux Graphics Intel Network Drivers ● Intel releases code GPL/BSD ● Internally developed ● Intel develops Linux driver ● Intel releases GPL code for Linux ● Community ports to FreeBSD and BSD code for FreeBSD ● Work required from community ● No work required from community ● Licenses can become mixed ● Licenses are clear ● Developed largely in the open ● Developed largely internally ● Easy for community to contribute ● Difficult to take community contributions Agenda ● Introduction (OTC & Me) ● Intel’s past involvement with BSD Intel’s Past Contributions ● 2011 ○ jimharris@ started on integrated SAS controller in the Intel C600 ● 2012 ○ jimharris@ merged isci(4), nvme(4), nvd(4), nvmecontrol(8) ● 2013 ○ NTB (Non-Transparent Bridge) driver (by carl@) ○ jimharris@ ported VTune
    [Show full text]
  • Using Upstream MPTCP in Linux Systems
    Using Upstream MPTCP in Linux Systems Mat Martineau and Ossama Othman Intel United States of America [email protected], [email protected] ​ ​ Abstract data stream. The MPTCP layer provides both outgoing data Multipath TCP patches have been merged for inclusion in and the necessary sequence numbers to the TCP stack to the Linux kernel, v5.6 and later. A community effort use when populating the MPTCP option headers at has been ongoing to develop an upstream-friendly kernel transmit time. For incoming packets, the subflow data patch set, with patches merged in 2020 that implement stream and the corresponding MPTCP-level sequence MPTCP capability according to RFC 8684 (MPTCP v1). Complementing this set of kernel patches is a numbers are passed up to the MPTCP layer where the userspace reference implementation for the MPTCP combined data stream is reassembled. Even though the generic netlink API called the Multipath TCP Daemon, TCP subflows deliver independent reassembled data i.e. "mptcpd". The Multipath TCP Daemon provides an streams to the MPTCP layer, those streams may contain extensible framework for MPTCP path management. redundant or out-of-order data for MPTCP to use when reassembling at the upper layer. The MPTCP option is also used while establishing Keywords connections, for the initial subflow or when adding MPTCP, Multipath, TCP subflows to an existing MPTCP connection. Additional MPTCP-related information is exchanged during the Introduction SYN/SYN-ACK/ACK handshake in either case. If the two peers do not both support the same MPTCP version during Multipath TCP (MPTCP) has been added to the upstream the initial connection process, a regular TCP connection is Linux kernel during the first half of 2020.
    [Show full text]
  • Unreliable Guide to Hacking the Linux Kernel Release 4.13.0-Rc4+
    Unreliable Guide To Hacking The Linux Kernel Release 4.13.0-rc4+ The kernel development community Sep 05, 2017 CONTENTS 1 Unreliable Guide To Hacking The Linux Kernel 1 1.1 Introduction ................................................. 1 1.2 The Players ................................................. 1 1.3 Some Basic Rules .............................................. 3 1.4 ioctls: Not writing a new system call .................................. 3 1.5 Recipes for Deadlock ............................................ 4 1.6 Common Routines ............................................. 4 1.7 Wait Queues include/linux/wait.h .................................. 7 1.8 Atomic Operations ............................................. 8 1.9 Symbols ................................................... 8 1.10 Routines and Conventions ......................................... 9 1.11 Putting Your Stuff in the Kernel ...................................... 10 1.12 Kernel Cantrips ............................................... 11 1.13 Thanks .................................................... 12 2 Unreliable Guide To Locking 13 2.1 Introduction ................................................. 13 2.2 The Problem With Concurrency ...................................... 13 2.3 Locking in the Linux Kernel ........................................ 14 2.4 Hard IRQ Context .............................................. 16 2.5 Cheat Sheet For Locking .......................................... 16 2.6 The trylock Functions ..........................................
    [Show full text]
  • Free Software and Proprietary Software a History of Free Software the FOSS Development Model FOSS Business Model Conclusion
    Free Software and Proprietary Software A History of Free Software The FOSS development model FOSS business model Conclusion Free Software Free as in freedom Josep M. Rib´o Universitat de Lleida January 22, 2009 Josep M. Rib´o Free Software Free Software and Proprietary Software A History of Free Software The FOSS development model FOSS business model Conclusion Outline 1 Free Software and Proprietary Software 2 A History of Free Software The first years 1980s: The begining of the Free Software Movement 1990s: Linux 2000s: The present of FOSS 3 The FOSS development model The Bazaar Infrastructure for FOSS projects 4 FOSS business model A collection of FOSS business models Community projects vs. corporate projects 5 Conclusion Josep M. Rib´o Free Software Free Software and Proprietary Software A History of Free Software The FOSS development model FOSS business model Conclusion You buy a brand new car..... Congratulations!!!! But unfortunatelly, its hood is locked and the seller has not given you the key :-( If you want to fix some add-ons or if the car breaks down you have to pay a visit to the Official Service (the only ones who have the key of the hood) ... and what will happen? Josep M. Rib´o Free Software Free Software and Proprietary Software A History of Free Software The FOSS development model FOSS business model Conclusion The official service The price is guaranteed to be excessive There is no competition (monopoly) It hinders the development of a network of local garage workshops It prevents you from fixing it yourself (provided you have mechanics knowledge) In a few years there will not be any maintenance for that car forcing you to buy a new one Would you buy a product like this? Well...
    [Show full text]
  • Open Source Software License Information
    Open Source Software license information This document contains an open source software license information for the product VACUU·SELECT. The product VACUU·SELECT contains open source components which are licensed under the applicable open source licenses. The applicable open source licenses are listed below. The open source software licenses are granted by the respective right holders directly. The open source licenses prevail all other license information with regard to the respective open source software components contained in the product. Modifications of our programs which are linked to LGPL libraries are permitted for the customer's own use and reverse engineering for debugging such modifications. However, forwarding the information acquired during reverse engineering or debugging to third parties is prohibited. Furthermore, it is prohibited to distribute modified versions of our programs. In any case, the warranty for the product VACUU·SELECT will expire, as long as the customer cannot prove that the defect would also occur without these modification. WARRANTY DISCLAIMER THE OPEN SOURCE SOFTWARE IN THIS PRODUCT IS DISTRIBUTED IN THE HOPE THAT IT WILL BE USEFUL, BUT WITHOUT ANY WARRANTY, WITHOUT EVEN THE IMPLIED WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. See the applicable licenses for more details. Written offer This product VACUU·SELECT contains software components that are licensed by the holder of the rights as free software, or Open Source software, under GNU General Public License, Versions 2 and 3, or GNU Lesser General Public License, Versions 2.1, or GNU Library General Public License, Version 2, respectively. The source code for these software components can be obtained from us on a data carrier (e.g.
    [Show full text]