DOCSLIB.ORG

Towards Practical Default-On Multi-Core Record/Replay

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Towards Practical Default-On Multi-Core Record/Replay Towards Practical Default-On Multi-Core Record/Replay Ali Jose´ Mashtizadeh Tal Garfinkel David Terei Stanford University Stanford University Stanford University [email protected] [email protected] [email protected] David Mazieres` Mendel Rosenblum Stanford University Stanford University http://www.scs.stanford.edu/~dm/ [email protected] Abstract 1. Introduction We present Castor, a record/replay system for multi-core Record/replay is used in a wide range of open source and applications that provides consistently low and predictable commercial applications: replay debugging [1–3, 36], can overheads. With Castor, developers can leave record and record difficult bugs when they occur and reproduce them replay on by default, making it practical to record and offline, decoupled analysis [2], can record execution online reproduce production bugs, or employ fault tolerance to with low overhead then replay it offline with high overhead recover from hardware failures. dynamic analysis tools, and hardware fault tolerance [14, 41], Castor is inspired by several observations: First, an effi- can record execution and replay it on a separate machine to cient mechanism for logging non-deterministic events is criti- enable real-time failover when hardware failures occur. cal for recording demanding workloads with low overhead. Unfortunately, the performance overhead of record/replay Through careful use of hardware we were able to increase log systems is frequently prohibitive, particularly in multi-core throughput by 10× or more, e.g., we could record a server settings. Often this limits their use to test and development handling 10× more requests per second for the same record environments and makes them impractical for implementing overhead. Second, most applications can be recorded without fault tolerance [5]. modifying source code by using the compiler to instrument language level sources of non-determinism, in conjunction Our goal with Castor is to provide record/reply with with more familiar techniques like shared library interposi- low enough overheads that developers are willing to leave tion. Third, while Castor cannot deterministically replay all recording on by default [17, 45], making it practical to record data races, this limitation is generally unimportant in practice, and reproduce difficult production bugs, or to enable fault contrary to what prior work has assumed. tolerance in high performance network services. Castor currently supports applications written in C, C++, The widespread use of multi-core architectures poses a and Go on FreeBSD. We have evaluated Castor on parallel key challenge to achieving this goal. Record/replay systems and server workloads, including a commercial implementa- work by recording and replaying non-deterministic program tion of memcached in Go, which runs Castor in production. inputs. Multi-core architectures introduce a new source of non-determinism in the form of shared memory interactions, CCS Concepts • Software and its engineering ! Oper- most frequently for synchronization between threads running ating systems on separate cores. Open source [36], commercial [1, 2] and some research Keywords Multi-Core Replay, Replay Debugging, Fault- systems [20] cope with this challenge by eliminating multi- Tolerance core execution, and its resultant non-determinism, by deter- ministically scheduling all threads on a single core. Other Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without research systems constrain and record non-determinism by fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than the author(s) must statically or dynamically adding and recording synchroniza- be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected]. tion [19, 26, 30], or use speculative execution [8, 29, 37, 49] ASPLOS ’17 April 8–12, 2017, Xi’an, China. to find a deterministic replay. These approaches have signifi- c 2017 Copyright held by the owner/author(s). Publication rights licensed to ACM. ISBN 978-1-4503-4465-4/17/04. $15.00 cant runtime overhead and scalability issues that limit their DOI: http://dx.doi.org/10.1145/3037697.3037751 usefulness for production workloads. Another approach is possible that avoids these overheads. has been concern that this could undermine the usefulness When source code is available, explicit synchronization—e.g., of replay [29, 30] by interfering with fault tolerance or bug locks, language-level atomics, or (in legacy code) volatile reproducibility. However, this limitation is of negligible im- variables—can be directly instrumented to capture and record portance today for several reasons. inter-thread non-determinism [18, 22, 23, 39]. Castor builds First, modern languages no longer support “benign data on this approach with several new observations: races,” i.e., races intentionally included for performance. Hardware-optimized logging is essential for keeping Any benefits they offered in the past are now supported record/replay overheads low as core counts and workload through relaxed-memory-order atomics [11]. Thus, all data intensities increase. Non-deterministic events, such as system races are undefined behavior, i.e., bugs on the same order as calls and synchronization, are recorded to and replayed from dereferencing a NULL pointer [12, 47]. a log. Maximizing log throughput is critical, since record Next, data races appear exceedingly rare relative to other overheads increase in proportion to the log throughput con- bugs, thus are unlikely to interfere with reproducing other sumed, modulo cache effects. Simply put, the more resources bugs on replay. For example, over a four-year period, there we spend on logging, e.g., CPU, memory bandwidth, the less were 165 data races found in the Chromium code base, 131 the application has to accomplish real work. of which were found by a race detector, compared to 65,861 Castor maximizes log throughput by eliminating con- total bugs, or about 1 in 400. Further, none of these bugs made tention. For example, hardware synchronized time stamp it into release builds, so at least in this example, data races counters are used as a contention-free source of ordering for would likely have no impact on the production use of replay. events. This and other optimizations improve log throughput Other studies of data races suggest that most do not introduce by a factor of 3×–10× or more—e.g., if recording a web sufficient non-determinism to impact replay [25, 34], and server with a given amount of load imposes a 2% overhead when they do, there are often viable ways of coping. We without these optimization, with them, we can record 3×– explore this further in x6. 10× more load (requests per second), for the same 2%. Castor works with normal debugging, analysis and profil- Minimizing log latency is also critical, as it directly ing tools such as gdb, lldb, valgrind, and pmcstat. It can impacts application response times. For example, if a thread is also replay modified binaries, enabling the use of ThreadSan- descheduled during a performance-critical logging operation, itizer and similar tools by recompiling and relinking before it can introduce delay, as other application threads that depend replay. Special asserts and printfs can also be added after on the pending operation are prevented from making forward the fact. We discuss using Castor, along with its performance progress. This can result in user-visible performance spikes. on server and parallel workloads in x5. To prevent this, we make use of a unique property of transactional memory which forces transactions to abort on protection ring crossings. This ensures that performance 2. Overview critical operations will abort if they are descheduled, thus preventing delay. We discuss logging further in x3. Castor records program execution by writing the outcome of Record/replay can often be enabled transparently, i.e., non-deterministic events to a log so they can be reproduced without any program modification. Castor and similar sys- at replay time, as depicted in Figure 1. tems record sources of non-determinism, such as synchro- Two types of non-determinism are recorded: input non- nization, by instrumenting source code. Other systems do determinism and ordering non-determinism. Input non- this manually, e.g., developers replace user level locks with determinism occurs when an input changes from one ex- wrapper functions. Manual instrumentation can be tedious ecution to another, such as network data from a recv system and error prone, often does not support all sources of non- call, or the random number returned by a RDRAND instruc- determinism, and can introduce additional and unpredictable tion; in these cases, we record the input to the log. Ordering performance overheads. non-determinism occurs when the order operations happen in To avoids this, Castor uses a custom LLVM compiler pass changes the outcome of an execution—for example, the order to automatically record user level non-determinism including that two threads read data from the same socket or acquire a atomics, ad hoc synchronization with volatiles, compiler lock. In these cases, we also record a counter that captures intrinsics, and inline
Load more

Recommended publications
  • Hoja De Datos De Familes Del Procesador Intel(R) Core(TM) De 10A Generación, Vol.1
    10a generación de familias de procesadores Intel® Core™ Ficha técnica, Volumen 1 de 2 Compatible con la 10a generación de la familia de procesadores Intel® Core™, procesadores Intel® Pentium®, procesadores Intel® Celeron® para plataformas U/Y, anteriormente conocidos como Ice Lake. Agosto de 2019 Revisión 001 Número del Documento: 341077-001 Líneas legales y descargos de responsabilidad Esta información es una combinación de una traducción hecha por humanos y de la traducción automática por computadora del contenido original para su conveniencia. Este contenido se ofrece únicamente como información general y no debe ser considerada como completa o precisa. No puede utilizar ni facilitar el uso de este documento en relación con ninguna infracción u otro análisis legal relacionado con los productos Intel descritos en este documento. Usted acepta conceder a Intel una licencia no exclusiva y libre de regalías a cualquier reclamación de patente redactada posteriormente que incluya el objeto divulgado en este documento. Este documento no concede ninguna licencia (expresa o implícita, por impedimento o de otro tipo) a ningún derecho de propiedad intelectual. Las características y beneficios de las tecnologías Intel dependen de la configuración del sistema y pueden requerir la activación de hardware, software o servicio habilitado. El desempeño varía según la configuración del sistema. Ningún equipo puede ser absolutamente seguro. Consulte al fabricante de su sistema o su distribuidor minorista u obtenga más información en intel.la. Las tecnologías Intel pueden requerir la activación de hardware habilitado, software específico o servicios. Consulte con el fabricante o distribuidor del sistema. Los productos descritos pueden contener defectos de diseño o errores conocidos como erratas que pueden hacer que el producto se desvíe de las especificaciones publicadas.
    [Show full text]
  • GPU Developments 2018
    GPU Developments 2018 2018 GPU Developments 2018 © Copyright Jon Peddie Research 2019. All rights reserved. Reproduction in whole or in part is prohibited without written permission from Jon Peddie Research. This report is the property of Jon Peddie Research (JPR) and made available to a restricted number of clients only upon these terms and conditions. Agreement not to copy or disclose. This report and all future reports or other materials provided by JPR pursuant to this subscription (collectively, “Reports”) are protected by: (i) federal copyright, pursuant to the Copyright Act of 1976; and (ii) the nondisclosure provisions set forth immediately following. License, exclusive use, and agreement not to disclose. Reports are the trade secret property exclusively of JPR and are made available to a restricted number of clients, for their exclusive use and only upon the following terms and conditions. JPR grants site-wide license to read and utilize the information in the Reports, exclusively to the initial subscriber to the Reports, its subsidiaries, divisions, and employees (collectively, “Subscriber”). The Reports shall, at all times, be treated by Subscriber as proprietary and confidential documents, for internal use only. Subscriber agrees that it will not reproduce for or share any of the material in the Reports (“Material”) with any entity or individual other than Subscriber (“Shared Third Party”) (collectively, “Share” or “Sharing”), without the advance written permission of JPR. Subscriber shall be liable for any breach of this agreement and shall be subject to cancellation of its subscription to Reports. Without limiting this liability, Subscriber shall be liable for any damages suffered by JPR as a result of any Sharing of any Material, without advance written permission of JPR.
    [Show full text]
  • SIMD Extensions
    SIMD Extensions PDF generated using the open source mwlib toolkit. See http://code.pediapress.com/ for more information. PDF generated at: Sat, 12 May 2012 17:14:46 UTC Contents Articles SIMD 1 MMX (instruction set) 6 3DNow! 8 Streaming SIMD Extensions 12 SSE2 16 SSE3 18 SSSE3 20 SSE4 22 SSE5 26 Advanced Vector Extensions 28 CVT16 instruction set 31 XOP instruction set 31 References Article Sources and Contributors 33 Image Sources, Licenses and Contributors 34 Article Licenses License 35 SIMD 1 SIMD Single instruction Multiple instruction Single data SISD MISD Multiple data SIMD MIMD Single instruction, multiple data (SIMD), is a class of parallel computers in Flynn's taxonomy. It describes computers with multiple processing elements that perform the same operation on multiple data simultaneously. Thus, such machines exploit data level parallelism. History The first use of SIMD instructions was in vector supercomputers of the early 1970s such as the CDC Star-100 and the Texas Instruments ASC, which could operate on a vector of data with a single instruction. Vector processing was especially popularized by Cray in the 1970s and 1980s. Vector-processing architectures are now considered separate from SIMD machines, based on the fact that vector machines processed the vectors one word at a time through pipelined processors (though still based on a single instruction), whereas modern SIMD machines process all elements of the vector simultaneously.[1] The first era of modern SIMD machines was characterized by massively parallel processing-style supercomputers such as the Thinking Machines CM-1 and CM-2. These machines had many limited-functionality processors that would work in parallel.
    [Show full text]
  • Demystifying Internet of Things Security Successful Iot Device/Edge and Platform Security Deployment — Sunil Cheruvu Anil Kumar Ned Smith David M
    Demystifying Internet of Things Security Successful IoT Device/Edge and Platform Security Deployment — Sunil Cheruvu Anil Kumar Ned Smith David M. Wheeler Demystifying Internet of Things Security Successful IoT Device/Edge and Platform Security Deployment Sunil Cheruvu Anil Kumar Ned Smith David M. Wheeler Demystifying Internet of Things Security: Successful IoT Device/Edge and Platform Security Deployment Sunil Cheruvu Anil Kumar Chandler, AZ, USA Chandler, AZ, USA Ned Smith David M. Wheeler Beaverton, OR, USA Gilbert, AZ, USA ISBN-13 (pbk): 978-1-4842-2895-1 ISBN-13 (electronic): 978-1-4842-2896-8 https://doi.org/10.1007/978-1-4842-2896-8 Copyright © 2020 by The Editor(s) (if applicable) and The Author(s) This work is subject to copyright. All rights are reserved by the Publisher, whether the whole or part of the material is concerned, specifically the rights of translation, reprinting, reuse of illustrations, recitation, broadcasting, reproduction on microfilms or in any other physical way, and transmission or information storage and retrieval, electronic adaptation, computer software, or by similar or dissimilar methodology now known or hereafter developed. Open Access This book is licensed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits use, sharing, adaptation, distribution and reproduction in any medium or format, as long as you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license and indicate if changes were made. The images or other third party material in this book are included in the book’s Creative Commons license, unless indicated otherwise in a credit line to the material.
    [Show full text]
  • FAST HASHING in CUDA Neville Walo Department of Computer
    FAST HASHING IN CUDA Neville Walo Department of Computer Science ETH Zurich¨ Zurich,¨ Switzerland ABSTRACT cies, it is possible to use the compression function of SHA- Hash functions, such as SHA-256 [1], are extensively used 256 along with the Sarkar-Schellenberg composition prin- in cryptographic applications. However, SHA-256 cannot ciple [2] to create a parallel collision resistant hash function be parallelized due to sequential dependencies. Using the called PARSHA-256 [3]. Sarkar-Schellenberg composition principle [2] in combina- In this work, we try to accelerate hashing in CUDA [6]. tion with SHA-256 gives rise to PARSHA-256 [3], a parallel We have divided this project into two sub-projects. The first collision resistant hash function. We present efficient imple- one is the Bitcoin scenario, with the goal to calculate many mentations for both SHA-256 and PARSHA-256 in CUDA. independent SHA-256 computation in parallel. The second Our results demonstrate that for large messages PARSHA- case is PARSHA-256, where the goal is to implement the 256 can significantly outperform SHA-256. proposed algorithm efficiently in CUDA. Related work. To our knowledge there is no compara- ble implementation of PARSHA-256 which runs on a GPU. 1. INTRODUCTION There exists only the implementation of the original paper, Hash functions are one of the most important operations which uses multithreading [3]. On the other hand, there in cryptographic applications, like digital signature algo- are countless implementations of Bitcoin Miners in CUDA rithms, keyed-hash message authentication codes, encryp- [7, 8], as this was the most prominent way to mine Bitcoins tions and the generation of random numbers.
    [Show full text]
  • A Fast, Verified, Cross-Platform Cryptographic Provider
    EverCrypt: A Fast, Verified, Cross-Platform Cryptographic Provider Jonathan Protzenko∗, Bryan Parnoz, Aymeric Fromherzz, Chris Hawblitzel∗, Marina Polubelovay, Karthikeyan Bhargavany Benjamin Beurdouchey, Joonwon Choi∗x, Antoine Delignat-Lavaud∗,Cedric´ Fournet∗, Natalia Kulatovay, Tahina Ramananandro∗, Aseem Rastogi∗, Nikhil Swamy∗, Christoph M. Wintersteiger∗, Santiago Zanella-Beguelin∗ ∗Microsoft Research zCarnegie Mellon University yInria xMIT Abstract—We present EverCrypt: a comprehensive collection prone (due in part to Intel and AMD reporting CPU features of verified, high-performance cryptographic functionalities avail- inconsistently [78]), with various cryptographic providers able via a carefully designed API. The API provably supports invoking illegal instructions on specific platforms [74], leading agility (choosing between multiple algorithms for the same functionality) and multiplexing (choosing between multiple im- to killed processes and even crashing kernels. plementations of the same algorithm). Through abstraction and Since a cryptographic provider is the linchpin of most zero-cost generic programming, we show how agility can simplify security-sensitive applications, its correctness and security are verification without sacrificing performance, and we demonstrate crucial. However, for most applications (e.g., TLS, cryptocur- how C and assembly can be composed and verified against rencies, or disk encryption), the provider is also on the critical shared specifications. We substantiate the effectiveness of these techniques with
    [Show full text]
  • Extracting and Mapping Industry 4.0 Technologies Using Wikipedia
    Computers in Industry 100 (2018) 244–257 Contents lists available at ScienceDirect Computers in Industry journal homepage: www.elsevier.com/locate/compind Extracting and mapping industry 4.0 technologies using wikipedia T ⁎ Filippo Chiarelloa, , Leonello Trivellib, Andrea Bonaccorsia, Gualtiero Fantonic a Department of Energy, Systems, Territory and Construction Engineering, University of Pisa, Largo Lucio Lazzarino, 2, 56126 Pisa, Italy b Department of Economics and Management, University of Pisa, Via Cosimo Ridolfi, 10, 56124 Pisa, Italy c Department of Mechanical, Nuclear and Production Engineering, University of Pisa, Largo Lucio Lazzarino, 2, 56126 Pisa, Italy ARTICLE INFO ABSTRACT Keywords: The explosion of the interest in the industry 4.0 generated a hype on both academia and business: the former is Industry 4.0 attracted for the opportunities given by the emergence of such a new field, the latter is pulled by incentives and Digital industry national investment plans. The Industry 4.0 technological field is not new but it is highly heterogeneous (actually Industrial IoT it is the aggregation point of more than 30 different fields of the technology). For this reason, many stakeholders Big data feel uncomfortable since they do not master the whole set of technologies, they manifested a lack of knowledge Digital currency and problems of communication with other domains. Programming languages Computing Actually such problem is twofold, on one side a common vocabulary that helps domain experts to have a Embedded systems mutual understanding is missing Riel et al. [1], on the other side, an overall standardization effort would be IoT beneficial to integrate existing terminologies in a reference architecture for the Industry 4.0 paradigm Smit et al.
    [Show full text]
  • Application Specific Programmable Processors for Reconfigurable Self-Powered Devices
    C651etukansi.kesken.fm Page 1 Monday, March 26, 2018 2:24 PM C 651 OULU 2018 C 651 UNIVERSITY OF OULU P.O. Box 8000 FI-90014 UNIVERSITY OF OULU FINLAND ACTA UNIVERSITATISUNIVERSITATIS OULUENSISOULUENSIS ACTA UNIVERSITATIS OULUENSIS ACTAACTA TECHNICATECHNICACC Teemu Nyländen Teemu Nyländen Teemu University Lecturer Tuomo Glumoff APPLICATION SPECIFIC University Lecturer Santeri Palviainen PROGRAMMABLE Postdoctoral research fellow Sanna Taskila PROCESSORS FOR RECONFIGURABLE Professor Olli Vuolteenaho SELF-POWERED DEVICES University Lecturer Veli-Matti Ulvinen Planning Director Pertti Tikkanen Professor Jari Juga University Lecturer Anu Soikkeli Professor Olli Vuolteenaho UNIVERSITY OF OULU GRADUATE SCHOOL; UNIVERSITY OF OULU, FACULTY OF INFORMATION TECHNOLOGY AND ELECTRICAL ENGINEERING Publications Editor Kirsti Nurkkala ISBN 978-952-62-1874-8 (Paperback) ISBN 978-952-62-1875-5 (PDF) ISSN 0355-3213 (Print) ISSN 1796-2226 (Online) ACTA UNIVERSITATIS OULUENSIS C Technica 651 TEEMU NYLÄNDEN APPLICATION SPECIFIC PROGRAMMABLE PROCESSORS FOR RECONFIGURABLE SELF-POWERED DEVICES Academic dissertation to be presented, with the assent of the Doctoral Training Committee of Technology and Natural Sciences of the University of Oulu, for public defence in the Wetteri auditorium (IT115), Linnanmaa, on 7 May 2018, at 12 noon UNIVERSITY OF OULU, OULU 2018 Copyright © 2018 Acta Univ. Oul. C 651, 2018 Supervised by Professor Olli Silvén Reviewed by Professor Leonel Sousa Doctor John McAllister ISBN 978-952-62-1874-8 (Paperback) ISBN 978-952-62-1875-5 (PDF) ISSN 0355-3213 (Printed) ISSN 1796-2226 (Online) Cover Design Raimo Ahonen JUVENES PRINT TAMPERE 2018 Nyländen, Teemu, Application specific programmable processors for reconfigurable self-powered devices. University of Oulu Graduate School; University of Oulu, Faculty of Information Technology and Electrical Engineering Acta Univ.
    [Show full text]
  • 10Th Gen Intel® Core™ Processor Families Datasheet, Vol. 1
    10th Generation Intel® Core™ Processor Families Datasheet, Volume 1 of 2 Supporting 10th Generation Intel® Core™ Processor Families, Intel® Pentium® Processors, Intel® Celeron® Processors for U/Y Platforms, formerly known as Ice Lake July 2020 Revision 005 Document Number: 341077-005 Legal Lines and Disclaimers You may not use or facilitate the use of this document in connection with any infringement or other legal analysis concerning Intel products described herein. You agree to grant Intel a non-exclusive, royalty-free license to any patent claim thereafter drafted which includes subject matter disclosed herein. No license (express or implied, by estoppel or otherwise) to any intellectual property rights is granted by this document. Intel technologies' features and benefits depend on system configuration and may require enabled hardware, software or service activation. Performance varies depending on system configuration. No computer system can be absolutely secure. Check with your system manufacturer or retailer or learn more at intel.com. Intel technologies may require enabled hardware, specific software, or services activation. Check with your system manufacturer or retailer. The products described may contain design defects or errors known as errata which may cause the product to deviate from published specifications. Current characterized errata are available on request. Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade. All information provided here is subject to change without notice. Contact your Intel representative to obtain the latest Intel product specifications and roadmaps Copies of documents which have an order number and are referenced in this document may be obtained by calling 1-800-548- 4725 or visit www.intel.com/design/literature.htm.
    [Show full text]
  • Oracle Solaris 10 113 Release Notes
    Oracle® Solaris 10 1/13 Release Notes Part No: E29493–01 January 2013 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 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. As such, use, duplication, disclosure, modification, and adaptation of the programs, including anyoperating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government. This software or hardware is developed for general use in a variety of information management applications.
    [Show full text]
  • Família De Processadores Intel® Core™ Da 10ª Geração
    Família de processadores Intel® Core™ da 10ª geração Datasheet, Volume 1 de 2 Apoiando a família de processadores Intel® Core™ da 10ª geração, processadores Intel® Pentium®, processadores Intel® Celeron® para plataformas U, anteriormente conhecido como Ice Lake Agosto de 2019 Revisão 001 Número do documento: 341077-001 Linhas legais e isenções de responsabilidade Para a sua conveniência, o conteúdo deste site foi traduzido utilizando-se uma combinação de programas de computador de tradução automática e tradutores. Este conteúdo é fornecido somente como informação de caráter genérico, não devendo ser considerado como uma tradução completamente correta do idioma original. Você não pode usar ou facilitar o uso deste documento em conexão com qualquer violação ou outra análise jurídica sobre produtos Intel descritos aqui. Você concorda em conceder à Intel uma licença não exclusiva e livre de royalties para qualquer pedido de patente, posteriormente redigido, que inclua o assunto divulgado aqui. Nenhuma licença (expressa ou implícita, por estoppel ou de outra forma) a quaisquer direitos de propriedade intelectual é concedida por este documento. Os recursos e benefícios das tecnologias Intel dependem da configuração do sistema e podem exigir ativação ativa de hardware, software ou serviço. O desempenho varia de acordo com a configuração do sistema. Nenhum sistema de computador é totalmente seguro. Consulte o fabricante ou revendedor do varejo de seu sistema, ou saiba mais em Intel.com. As tecnologias Intel podem exigir ativação de hardware, software específico ou serviços habilitados. Verifique com o fabricante do sistema ou varejista. Os produtos descritos podem conter defeitos de design ou erros conhecidos como errata que podem fazer com que o produto se desvie das especificações publicadas.
    [Show full text]
  • Datasheet Product Features
    Intel® IXP42X Product Line of Network Processors and IXC1100 Control Plane Processor Datasheet Product Features For a complete list of product features, see “Product Features” on page 9. ■ Intel XScale® Core ■ Encryption/Authentication ■ Three Network Processor Engines ■ High-Speed UART ■ PCI Interface ■ Console UART ■ Two MII Interfaces ■ Internal Bus Performance Monitoring Unit ■ UTOPIA-2 Interface ■ 16 GPIOs ■ USB v 1.1 Device Controller ■ Four Internal Timers ■ Two High-Speed, Serial Interfaces ■ Packaging ■ SDRAM Interface —492-pin PBGA —Commercial/Extended Temperature Typical Applications ■ High-Performance DSL Modem ■ Control Plane ■ High-Performance Cable Modem ■ Integrated Access Device (IAD) ■ Residential Gateway ■ Set-Top Box ■ SME Router ■ Access Points (802.11a/b/g) ■ Network Printers ■ Industrial Controllers Document Number: 252479-004 June 2004 Intel® IXP42X Product Line and IXC1100 Control Plane Processor INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTELR PRODUCTS. EXCEPT AS PROVIDED IN INTEL'S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER, AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY RELATING TO SALE AND/OR USE OF INTEL PRODUCTS, INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT, OR OTHER INTELLECTUAL PROPERTY RIGHT. Intel Corporation may have patents or pending patent applications, trademarks, copyrights, or other intellectual property rights that relate to the presented subject matter. The furnishing of documents and other materials and information does not provide any license, express or implied, by estoppel or otherwise, to any such patents, trademarks, copyrights, or other intellectual property rights. Intel products are not intended for use in medical, life saving, life sustaining, critical control or safety systems, or in nuclear facility applications.
    [Show full text]