DOCSLIB.ORG

Notice for Netapp HCI

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

  1056
Copy Link
Notice About this document The following copyright statements and licenses apply to software components that are distributed with various versions of the NetApp HCI products. Your product does not necessarily use all the software components referred to below. Where required, source code is published at the following location: https://opensource.netapp.com/ 1 Notice Copyrights and licenses The following component(s) is(are) subject to the AESLib License (BSD 2.0 -) • AESLib License contribution to skein - Unspecified Copyright (c) 2003, Dr Brian Gladman, Worcester, UK. All rights reserved. AESLib License (BSD 2.0 -) Copyright (c) 2003, Copera, Inc., Mountain View, CA, USA. All rights reserved. LICENSE TERMS The free distribution and use of this software in both source and binary form is allowed (with or without changes) provided that: 1. distributions of this source code include the above copyright notice, this list of conditions and the following disclaimer; 2. distributions in binary form include the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other associated materials; 3. the copyright holder's name is not used to endorse products built using this software without specific written permission. DISCLAIMER This software is provided 'as is' with no explcit or implied warranties in respect of any properties, including, but not limited to, correctness and fitness for purpose. ------------------------------------------------------------------------- Issue Date: March 10, 2003 2 Notice The following component(s) is(are) subject to the Apache 1.1 • Apache Base64 functions - Unspecified Copyright (c) 1995-1999 The Apache Group. All rights reserved. Apache Software License Version 1.1 Copyright (c) 2000 The Apache Software Foundation. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment: "This product includes software developed by the Apache Software Foundation (http://www.apache.org/)." Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear. 4. The names "Apache" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected]. 3 Notice 5. Products derived from this software may not be called "Apache", nor may "Apache" appear in their name, without prior written permission of the Apache Software Foundation. THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation. For more information on the Apache Software Foundation, please see <http://www.apache.org/>. Portions of this software are based upon public domain software originally written at the National Center for Supercomputing Applications, University of Illinois, Urbana-Champaign. 4 Notice The following component(s) is(are) subject to the Apache License Version 2.0 • httplib-cachecontrol - Unspecified • msgpack-python - Unspecified • packaging - pypa/packaging - 16.8 Copyright (c) 2005-2010 ActiveState Software Inc. Copyright (c) 2013 Eddy PetriÈor Copyright (c) 2003-2018 Paul T. McGuire • requests - 2.19.1 Copyright (c) 2012 by Kenneth Reitz. • Tornado Web Server (tornadoweb) - Unspecified Copyright 2012 Facebook • Apache 2.0 contributions to Q in javascript - Unspecified Copyright (C) 2011 Google Inc. • Bootstrap (Twitter) - 3.3.7 Copyright 2011-2015 Twitter, Inc. • Apache 2.0 Contribution to OpenSSL - Unspecified Copyright 2014 Intel Corporation. Copyright 2011 Google Inc. 5 Notice • Apache contribution to avahi - unspecified • Apache 2.0 Contributions to Linux kernel - Unspecified Copyright (C) 2017-2018 HUAWEI, Inc. • Kubernetes Helm - 3.2.1 Copyright 2016 The Kubernetes Authors All Rights Reserved • requests - 2.13.0 Copyright 2016 Kenneth Reitz • rtslib-fb - 2.1.69 Copyright (c) 2011-2014 by Red Hat, Inc. Copyright (c) 2011-2013 by Datera, Inc. • sf-k8s-octant - 0.10.2 Copyright (c) 2011-2018, Christopher Jeffrey (https://github.com/chjj/) Copyright (c) 2016-2018 Google, Inc. Copyright (c) 2012-2014 Chris Pettitt Copyright (c) 2014-2018 Michael Daines Copyright 2010-2016 Mike Bostock All rights reserved. • targetcli-fb - 2.1.49 6 Notice Copyright (c) 2011-2013 by Datera, Inc. • Apache 2.0 contributions to boto - Unspecified • Apache 2.0 contributions to Mozilla NSS - Unspecified • Apache contribution to ISC-DHCP - Unspecified Copyright (c) 2014 by Farsight Security, Inc • bpftrace - 0.9.2 Copyright 2018 Netflix, Inc. Copyright (c) 2018 Dale Hamel. Copyright (c) 2008 Eli Friedman Copyright 2019 Alastair Robertson Copyright (c) 2014 Chandler Carruth • configshell-fb - 1.1.24 Copyright (c) 2011-2013 by Datera, Inc • coverage.py - 5.0 Copyright 2004-2019 Ned Batchelder. All rights reserved. Copyright 2001 Gareth Rees. All rights reserved. • cryptography - 2.0.3 7 Notice Copyright 2001-2016 Python Software Foundation; All Rights Reserved. • pyca/cryptography - 2.6.1 Copyright 2001-2016 Python Software Foundation; All Rights Reserved. Copyright (c) Individual contributors. All rights reserved. • Apache 2.0 contribution to collectd - Unspecified Copyright 2006 Alexander Wirt • Apache Contributions to Git - Unspecified Copyright 2012 Google, Inc. • BPF Compiler Collection - 0.10.0 Copyright (c) PLUMgrid, Inc. • buildkit - Unspecified • bz2file - 0.98 • cameroncox-mousetrap - Unspecified Copyright 2014 Alan Shreve • cli (github.com/proofpoint/discovery) - Unspecified • client-model - Unspecified • client_golang - 0.8.0 Copyright 2011 The Go Authors. Copyright 2012 The Go Authors. Copyright 2013 The Go Authors. 8 Notice Copyright 2009 The Go Authors. Copyright 2010 The Go Authors. Copyright 2014 The Go Authors. • com.google.cloud.bigtable:bigtable-client-core - Unspecified Copyright 2014 Google Inc. • common (github.com/doctrine/common) - Unspecified Copyright 2015 The Prometheus Authors • containerd-console - 2748ece16665b45a47f884001d5831ec79703880 • containerd/containerd - 1.2.6 Copyright The containerd Authors. • coreos-go-semver - Unspecified Copyright 2013-2015 CoreOS, Inc. Copyright 2014 Docker, Inc. • coreos-pkg - 3 Copyright 2016 CoreOS, Inc. • coreos-pkg - Unspecified • dnstap-ldns - Unspecified 9 Notice Copyright (c) 2016-2017 Farsight Security • docker - 18.09.8 Copyright (c) 2012-2017 Docker, Inc. • docker-cli-js - Unspecified • docker-containerd - 1.0.1 Copyright (C) 1999-2008 Novell Inc. Copyright 2009-2012 Canonical Ltd. Copyright (C) 2004, 2006 The Linux Foundation and its contributors. Copyright 2013-2016 Docker, Inc. Copyright 2012-2015 Docker, Inc. Copyright 2017 Google Inc. • docker-distribution - Unspecified Copyright (c) 2012-2017 Docker, Inc. • docker-go-connections - Unspecified Copyright 2012 The Go Authors. All rights reserved. • docker-go-units - 0.2.0 10 Notice copyright (c) 2012 - 2016 Docker • docker-go-units - Unspecified copyright (c) 2012 - 2016 Docker • docker-libkv - Unspecified • docker-libnetwork - Unspecified Copyright 2014 Vishvananda Ishaya. Copyright 2014 Docker, Inc copyright 2015 Docker, inc • docker-libtrust - Unspecified Copyright 2014 - 2016 Docker, Inc. • docker-notary - Unspecified Copyright (c) 2014-2015 Prime Directive, Inc. All rights reserved. Copyright (c) 2015, Docker Inc. • docker-proxy - 0.8.0_p20190513 Copyright (c) 2012-2017 Docker, Inc. Copyright 2012-2016 Docker, Inc. Copyright 2012 The Go Authors. All rights reserved. • etcd - 3.1.5 11 Notice Copyright (c) 2015 CoreOS, Inc Copyright 2015 The etcd Authors • exp - Unspecified Copyright 2012-2017 Docker, Inc. Copyright 2015 The Prometheus Authors • fluent-fluent-logger-golang - Unspecified • flynn-go-shlex - Unspecified Copyright 2012 Google Inc. All Rights Reserved. • Funker for Go - Unspecified • gen-proto - Unspecified • go-criu - v3.11 • Go-digest - Unspecified • go-events - Unspecified Copyright 2016 Docker, Inc. Licensed under the Apache Copyright © 2016 Docker, Inc. go-events is licensed under the Apache License, Version 2.0. See [LICENSE](LICENSE • go-ini-ini - Unspecified Copyright 2014 Unknwon • go-pkg - Unspecified Copyright 2011-2016 Canonical Ltd. • go-systemd - 14 12 Notice Copyright 2015 CoreOS, Inc Copyright 2016 CoreOS, Inc • go-systemd - Unspecified Copyright
Recommended publications
  • Oracle Database Licensing Information, 11G Release 2 (11.2) E10594-26

    Oracle Database Licensing Information, 11G Release 2 (11.2) E10594-26

    Oracle® Database Licensing Information 11g Release 2 (11.2) E10594-26 July 2012 Oracle Database Licensing Information, 11g Release 2 (11.2) E10594-26 Copyright © 2004, 2012, Oracle and/or its affiliates. All rights reserved. Contributor: Manmeet Ahluwalia, Penny Avril, Charlie Berger, Michelle Bird, Carolyn Bruse, Rich Buchheim, Sandra Cheevers, Leo Cloutier, Bud Endress, Prabhaker Gongloor, Kevin Jernigan, Anil Khilani, Mughees Minhas, Trish McGonigle, Dennis MacNeil, Paul Narth, Anu Natarajan, Paul Needham, Martin Pena, Jill Robinson, Mark Townsend This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.
  • The Dragonflybsd Operating System

    The Dragonflybsd Operating System

    1 The DragonFlyBSD Operating System Jeffrey M. Hsu, Member, FreeBSD and DragonFlyBSD directories with slightly over 8 million lines of code, 2 million Abstract— The DragonFlyBSD operating system is a fork of of which are in the kernel. the highly successful FreeBSD operating system. Its goals are to The project has a number of resources available to the maintain the high quality and performance of the FreeBSD 4 public, including an on-line CVS repository with mirror sites, branch, while exploiting new concepts to further improve accessible through the web as well as the cvsup service, performance and stability. In this paper, we discuss the motivation for a new BSD operating system, new concepts being mailing list forums, and a bug submission system. explored in the BSD context, the software infrastructure put in place to explore these concepts, and their application to the III. MOTIVATION network subsystem in particular. A. Technical Goals Index Terms— Message passing, Multiprocessing, Network The DragonFlyBSD operating system has several long- operating systems, Protocols, System software. range technical goals that it hopes to accomplish within the next few years. The first goal is to add lightweight threads to the BSD kernel. These threads are lightweight in the sense I. INTRODUCTION that, while user processes have an associated thread and a HE DragonFlyBSD operating system is a fork of the process context, kernel processes are pure threads with no T highly successful FreeBSD operating system. Its goals are process context. The threading model makes several to maintain the high quality and performance of the FreeBSD guarantees with respect to scheduling to ensure high 4 branch, while exploring new concepts to further improve performance and simplify reasoning about concurrency.
  • Matthew Dillon Dragonfly BSD Project 23 October 2003 Dragonfly Overview

    Matthew Dillon Dragonfly BSD Project 23 October 2003 Dragonfly Overview

    Matthew Dillon DragonFly BSD Project 23 October 2003 DragonFly Overview ●FreeBSD 4.x and 5.x directions ●Differentiating DragonFly, the basis for a project fork ● A different, more maintainable user threading API (syscall messaging) ● A different, more maintainable approach to MP design ● CPU Isolation by design using IPI messaging rather then by accident w/Mutexes ● Light Weight Kernel Threading with fewer hacks ●Project Goals ● Maintaining stability, producing production-capable releases ● A more consistent and more easily maintained message-based framework ● UP, MP, SSI Scaleability ● Userland VFS Development ● Machine-verified Package Management ●This Presentation ● Threading And Messaging ● Our approach to the Big Giant Lock problem. Why not mutexes? ● Our approach to achieving a Single System Image (SSI) DragonFly Threading and Messaging Model Matthew Dillon DragonFly BSD Project 23 October 2003 Light Weight Kernel Threading and User Processes LWKT SUBSYSTEM USERLAND PROCESS SCHEDULER CPU #1 PROCESS RUNQ SCHEDULER THREAD LWKT SCHEDULER THREAD PROCESS1 (FIXED PRIORITY) PROCESS2 THREAD PROCESS2 CURPROC ON CPU1 PROCESS3 CPU #2 THREAD PROCESS4 LWKT SCHEDULER PROCESS5 THREAD PROCESS5 (FIXED PRIORITY) CURPROC ON CPU2 THREAD PROCESS6 IPI Messaging ●ABSTRACTION PROMOTES CPU ISOLATION ●ASYNCHRONOUS IPI MESSAGING AVOIDS MUTEX OPS ●SIMPLE CRITICAL SECTIONS FOR LOCAL ACCESS ●MANY IPI OPS CAN BE PASSIVE / CONTRAST W/ RCU CPU #1 CPU #2 SCHEDULER SCHEDULER ASYNC THREAD1 SCHEDULE IPI SCHEDULE THREAD2 THREAD2 MESSAGE THREAD2 ALLOCATOR ALLOCATE MEMORY
  • Evolutionary Tree-Structured Storage: Concepts, Interfaces, and Applications

    Evolutionary Tree-Structured Storage: Concepts, Interfaces, and Applications

    Evolutionary Tree-Structured Storage: Concepts, Interfaces, and Applications Dissertation submitted for the degree of Doctor of Natural Sciences Presented by Marc Yves Maria Kramis at the Faculty of Sciences Department of Computer and Information Science Date of the oral examination: 22.04.2014 First supervisor: Prof. Dr. Marcel Waldvogel Second supervisor: Prof. Dr. Marc Scholl i Abstract Life is subdued to constant evolution. So is our data, be it in research, business or personal information management. From a natural, evolutionary perspective, our data evolves through a sequence of fine-granular modifications resulting in myriads of states, each describing our data at a given point in time. From a technical, anti- evolutionary perspective, mainly driven by technological and financial limitations, we treat the modifications as transient commands and only store the latest state of our data. It is surprising that the current approach is to ignore the natural evolution and to willfully forget about the sequence of modifications and therefore the past state. Sticking to this approach causes all kinds of confusion, complexity, and performance issues. Confusion, because we still somehow want to retrieve past state but are not sure how. Complexity, because we must repeatedly work around our own obsolete approaches. Performance issues, because confusion times complexity hurts. It is not surprising, however, that intelligence agencies notoriously try to collect, store, and analyze what the broad public willfully forgets. Significantly faster and cheaper random-access storage is the key driver for a paradigm shift towards remembering the sequence of modifications. We claim that (1) faster storage allows to efficiently and cleverly handle finer-granular modifi- cations and (2) that mandatory versioning elegantly exposes past state, radically simplifies the applications, and effectively lays a solid foundation for backing up, distributing and scaling of our data.
  • Bsdcan-2018-Governance.Pdf (Application/Pdf

    Bsdcan-2018-Governance.Pdf (Application/Pdf

    The Evolution of FreeBSD Governance Marshall Kirk McKusick [email protected] http://www.mckusick.com Based on a paper written with Benno Rice The FreeBSD Journal, 4,5. September 2017, pp 26−31 BSDCan Conference Ottawa,Canada June 9, 2018 Copyright 2018 by Marshall Kirk McKusick 1 Background and Introduction The BerkeleySoftware Distribution (BSD) started in 1977 as a project of Bill Joy at the University of California at Berkeley Became a full distribution with the release of 3BSD for the VAX in 1979 Use of source-code control (SCCS) started in 1980 Adecade of releases were managed by the Computer Systems Research Group (CSRG), afour-person development team. Nearly-full open-source release of Net/2 in 1991 followed by 4.4BSD-Lite in 1994 2 The Formation of the FreeBSD Project FreeBSD was named on June 19, 1993 and wasderivedfrom Bill Jolitz version of 4.4BSD-Lite for the Intel 386 Managed under the CVS source-code control system Core team (with lifetime terms) created to decide who should be allowed to commit Initially distributed by Walnut Creek CDROM Separated into base system and ports to keep base system size managable GNATSwas brought up manage bug reports 3 The FreeBSD Project Movesinto Companies Yahoo ran entirely on FreeBSD and agreed to host CVS and distribution Justin Gibbs starts the FreeBSD Foundation aiming to provide the FreeBSD infrastructure Deadwood and apathy in the 20-member core team lead to creating bylaws that set up a 9-member elected core team First elected core team in 2000 with few carryovers from old core
  • Limits and the Practical Usability of Bsds, a Big Data Prospective

    Limits and the Practical Usability of Bsds, a Big Data Prospective

    Limits and the Practical Usability of BSDs, a Big Data Prospective Predrag Punosevacˇ [email protected] The Auton Lab Carnegie Mellon University June 11, 2016 1 / 22 Thanks Thanks to organizers for this great meeting and for giving me the op- portunity to speak. note 1 of slide 1 Intro ❖ Intro ● Who am I? ❖ Chronology ❖ Chronology II ❖ Genealogy Tree ❖ General Limitations ❖ Scientific Computing ❖ Continuation ❖ misc issues ❖ NetBSD ❖ OpenBSD ❖ pf.conf and pfctl ❖ OpenBSD cons ❖ FreeBSD ❖ TrueOS ❖ TurnKey Appliance ❖ FreeNAS ❖ pfSense ❖ DragonFly BSD ❖ HAMMER ❖ Dark Clouds ❖ References 2 / 22 Intro ❖ Intro ● Who am I? ❖ Chronology ❖ Chronology II ❖ Genealogy Tree ● What is the Auton Lab? ❖ General Limitations ❖ Scientific Computing ❖ Continuation ❖ misc issues ❖ NetBSD ❖ OpenBSD ❖ pf.conf and pfctl ❖ OpenBSD cons ❖ FreeBSD ❖ TrueOS ❖ TurnKey Appliance ❖ FreeNAS ❖ pfSense ❖ DragonFly BSD ❖ HAMMER ❖ Dark Clouds ❖ References 2 / 22 Intro ❖ Intro ● Who am I? ❖ Chronology ❖ Chronology II ❖ Genealogy Tree ● What is the Auton Lab? ❖ General Limitations ❖ Scientific ● Why don’t we just use SCS computing facilities? Computing ❖ Continuation ❖ misc issues ❖ NetBSD ❖ OpenBSD ❖ pf.conf and pfctl ❖ OpenBSD cons ❖ FreeBSD ❖ TrueOS ❖ TurnKey Appliance ❖ FreeNAS ❖ pfSense ❖ DragonFly BSD ❖ HAMMER ❖ Dark Clouds ❖ References 2 / 22 Intro ❖ Intro ● Who am I? ❖ Chronology ❖ Chronology II ❖ Genealogy Tree ● What is the Auton Lab? ❖ General Limitations ❖ Scientific ● Why don’t we just use SCS computing facilities? Computing ❖ Continuation ❖ misc issues ● How did
  • Commencement1990.Pdf (7.862Mb)

    Commencement1990.Pdf (7.862Mb)

    TheJohns Hopkins University Conferring of Degrees At the Close of the 1 14th Academic Year May 24, 1990 Digitized by the Internet Archive in 2012 with funding from LYRASIS Members and Sloan Foundation http://archive.org/details/commencement1990 Contents Order of Procession 1 Order of Events 2 Honorary Degree Citations 9 Academic Regalia 16 Awards 18 Honor Societies 22 Student Honors 25 Degree Candidates 28 Order of Procession MARSHALS Stephen R. Anderson Marion C. Panyan Andrew S. Douglas Peter B. Petersen Elliott W. Galkin Edward Scheinerman Grace E. Goodell Henry M. Seidel Sharon S. Krag Stella Shiber Bonnie J. Lake Susan Wolf Bruce D. Marsh Eric D. Young THE GRADUATES MARSHALS Jerome Kruger Dean W. Robinson THE FACULTIES to MARSHALS Frederic Davidson AJ.R. Russell-Wood THE DEANS OFFICERS OF THE UNIVERSITY THE TRUSTEES CHIEF MARSHAL Owen M. Phillips THE PRESIDENT OF THE JOHNS HOPKINS UNIVERSITY ALUMNI COUNCIL THE CHAPLAINS THE PRESENTERS OF THE HONORARY DEGREE CANDIDATES THE HONORARY DEGREE CANDIDATES THE INTERIM PROVOST OF THE UNIVERSITY THE GOVERNOR OF THE STATE OF MARYLAND THE CHAIRMAN OF THE BOARD OF TRUSTEES THE PRESIDENT OF THE UNIVERSITY - /- Order ofEvents Si even Muller President of the University, presiding * • 4 PRELUDE La Mourisque Tielman Susato (? -1561) Basse Dance Tielman Susato (? -1561) Two Ayres for Cornetts and Sagbuts JohnAdson (?- 1640) Sonata No. 22 Johann Pezel (1639-1694) » PROCESSIONAL The audience is requested to stand as the Academic Procession moves into the area and to remain standing after the Invocation. FESTIVAL MARCHES THE PRESIDENTS PROCESSION Fanfare Walter Piston (1894-1976) Pomp and Circumstance March No.
  • HAMMER and Postgresql Performance Jan Lentfer Oct. 2009

    HAMMER and Postgresql Performance Jan Lentfer Oct. 2009

    HAMMER and PostgreSQL Performance Jan Lentfer Oct. 2009 (document still being worked upon, intermediate version) System The system used for this test was an Intel Atom 330, Foxconn mainboard, 2 GB RAM and 2 Seagate Barracuda ES.2 250GB SATA II disks. The operating system was installed on the first disk, while all the PostgreSQL files (data) were installed on a 150GB partition on the 2 nd disk. Both disks operated on their own SATA channel. PostgreSQL PostgreSQL 8.3 was installed from binaries using the respective packaging system. In postgresql.conf Shared buffers were set to 512MB, Effective Cache Size to 1024MB. Otherwise default values from the Dragonfly BSD installation were used. The same postgresql.conf file was used on all Operating Systems. Dragonfly BSD The version used was 2.4.1. The Kernel was build using “make nativekernel”. The KERNCONF was a copy of GENERIC with these changes: --- GENERIC 2009-09-27 22:01:49 +0200 +++ ATOM_SMP 2009-10-11 00:42:24 +0200 @@ -9,10 +9,10 @@ platform pc32 machine i386 machine_arch i386 -cpu I486_CPU -cpu I586_CPU +#cpu I486_CPU +#cpu I586_CPU cpu I686_CPU -ident GENERIC +ident ATOM_SMP maxusers 0 makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols @@ -58,7 +58,7 @@ # boot fine for non-SMP builds *might* work in SMP mode # if you define SMP and leave APIC_IO turned off. # -#options SMP # Symmetric MultiProcessor Kernel +options SMP # Symmetric MultiProcessor Kernel #options APIC_IO # Symmetric (APIC) I/O # Debugging for Development The acpi kernel module was not loaded. Test Scenario pgbench was run from an Ubuntu Linux system on the same 100MBit switched network.
  • ULE: a Modern Scheduler for Freebsd

    ULE: a Modern Scheduler for Freebsd

    USENIX Association Proceedings of BSDCon ’03 San Mateo, CA, USA September 8–12, 2003 THE ADVANCED COMPUTING SYSTEMS ASSOCIATION © 2003 by The USENIX Association All Rights Reserved For more information about the USENIX Association: Phone: 1 510 528 8649 FAX: 1 510 548 5738 Email: [email protected] WWW: http://www.usenix.org Rights to individual papers remain with the author or the author's employer. Permission is granted for noncommercial reproduction of the work for educational or research purposes. This copyright notice must be included in the reproduced paper. USENIX acknowledges all trademarks herein. ULE: A Modern Scheduler For FreeBSD Jeff Roberson The FreeBSD Project [email protected] Abstract The existing thread scheduler in FreeBSD was well suited towards the computing environment that it was developed in. As the priorities and hardware targets of the project have changed, new features and scheduling properties were required. This paper presents ULE, a scheduler that is designed with modern hardware and requirements in mind. Prior to discussing ULE, the designs of several other schedulers are presented to provide some context for comparison. A simple scheduler profiling tool is also discussed, the results of which provide a basis for making simple comparisons between important aspects of several schedulers. 1 Motivation UP. These efforts were examined while ULE was under development and many of them had some The FreeBSD project began a considerable shift in influence in its design. ULE was intended to be a kernel architecture for the 5.0 release. The new production quality modern scheduler from the start. As architecture is geared towards SMP (Symmetric Multi- such evolution was preferred over revolution.
  • (FSS) in Oracle Cloud Infrastructure Bradley C

    (FSS) in Oracle Cloud Infrastructure Bradley C

    Everyone Loves File: File Storage Service (FSS) in Oracle Cloud Infrastructure Bradley C. Kuszmaul, Matteo Frigo, Justin Mazzola Paluska, and Alexander (Sasha) Sandler, Oracle Corporation https://www.usenix.org/conference/atc19/presentation/frigo This paper is included in the Proceedings of the 2019 USENIX Annual Technical Conference. July 10–12, 2019 • Renton, WA, USA ISBN 978-1-939133-03-8 Open access to the Proceedings of the 2019 USENIX Annual Technical Conference is sponsored by USENIX. Everyone Loves File: File Storage Service (FSS) in Oracle Cloud Infrastructure Bradley C. Kuszmaul Matteo Frigo Justin Mazzola Paluska Alexander (Sasha) Sandler Oracle Corporation Abstract 100 MB=s of bandwidth and 3000 operations per sec- ond for every terabyte stored. Customers can mount a File Storage Service (FSS) is an elastic filesystem pro- filesystem on an arbitrary number of NFS clients. The vided as a managed NFS service in Oracle Cloud In- size of a file or filesystem is essentially unbounded, lim- frastructure. Using a pipelined Paxos implementation, ited only by the practical concerns that the NFS pro- we implemented a scalable block store that provides lin- tocol cannot cope with files bigger than 16 EiB and earizable multipage limited-size transactions. On top of that we would need to deploy close to a million hosts the block store, we built a scalable B-tree that provides to store multiple exabytes. FSS provides the ability linearizable multikey limited-size transactions. By us- to take a snapshot of a filesystem using copy-on-write ing self-validating B-tree nodes and performing all B- techniques.
  • Proceedings of the Bsdcon 2002 Conference

    Proceedings of the Bsdcon 2002 Conference

    USENIX Association Proceedings of the BSDCon 2002 Conference San Francisco, California, USA February 11-14, 2002 THE ADVANCED COMPUTING SYSTEMS ASSOCIATION © 2002 by The USENIX Association All Rights Reserved For more information about the USENIX Association: Phone: 1 510 528 8649 FAX: 1 510 548 5738 Email: [email protected] WWW: http://www.usenix.org Rights to individual papers remain with the author or the author's employer. Permission is granted for noncommercial reproduction of the work for educational or research purposes. This copyright notice must be included in the reproduced paper. USENIX acknowledges all trademarks herein. Running ‘‘Fsck’’ in the Background Marshall Kirk McKusick Author and Consultant Abstract Traditionally, recovery of a BSD fast filesystem after an uncontrolled system crash such as a power failure or a system panic required the use of the filesystem checking program, ‘‘fsck’’. Because the filesystem cannot be used while it is being checked by ‘‘fsck’’, a large server may experience unacceptably long periods of unavailability after a crash. Rather than write a new version of ‘‘fsck’’ that can run on an active filesystem, I have added the ability to take a snapshot of a filesystem partition to create a quiescent filesystem on which a slightly modified version of the tradi- tional ‘‘fsck’’ can run. A key feature of these snapshots is that they usually require filesystem write activity to be suspended for less than one second. The suspension time is independent of the size of the filesystem. To reduce the number and types of corruption, soft updates were added to ensure that the only filesystem inconsistencies are lost resources.
  • Freebsd Handbook

    Freebsd Handbook

    FREEBSD HANDBOOK The FreeBSD Documentation Project For FreeBSD v.(4.6 and up)/5.x Published by Fultus Corporation FreeBSD Handbook by The FreeBSD Documentation Project Published February 1999 Copyright © 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002 by The FreeBSD Documentation Project Welcome to FreeBSD! This handbook covers the installation and day to day use of FreeBSD 4.6-RELEASE. This manual is a work in progress and is the work of many individuals. Many sections do not yet exist and some of those that do exist need to be updated. If you are in- terested in helping with this project, send email to the FreeBSD documentation project mail- ing list <[email protected]>. The latest version of this document is always avail- able from the FreeBSD web site (../../../../index.html). It may also be downloaded in a vari- ety of formats and compression options from the FreeBSD FTP server (ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/) or one of the numerous mirror sites. If you would prefer to have a hard copy of the handbook, you can purchase one at the FreeBSD Mall (www.freebsdmall.com). You may also want to search the handbook (../../../../search/index.html). Redistribution and use in source (SGML DocBook) and 'compiled' forms (SGML, HTML, PDF, PostScript, RTF and so forth) with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code (SGML DocBook) must retain the above copyright no- tice, this list of conditions and the following disclaimer as the first lines of this file unmodified.