《InfiniBand（IB）协议详解》 InfiniBand（IB）协议是一种高性能的、基于交换架构的互连技术，广泛应用于数据中心、高性能计算和存储领域。该技术最初由InfiniBand Trade Association（IBTA）制定，旨在提供低延迟、高带宽的数据传输。"IB Specification Vol 1-Release-1.4.pdf"是关于InfiniBand协议的详细规范文档，包含了协议的最新版本，即1.4版。 InfiniBand协议的核心在于其灵活的架构和先进的通信机制，其中RDMA（Remote Direct Memory Access）是其显著特征之一。RDMA允许数据直接在系统内存间传输，而无需经过操作系统内核，极大地减少了CPU的负担，提高了数据传输效率。这一特性使得InfiniBand在大数据处理和云计算环境中表现出色。 InfiniBand协议分为几个主要部分： 1. **基础架构**：InfiniBand架构由通道适配器（CA）、交换机（Switch）和物理链路组成。CA是连接到服务器或设备的接口，交换机则负责将数据包路由到正确的目标，物理链路则通过光纤或铜线进行数据传输。 2. **传输层**：包括RC（Reliable Connection）和UD（Unreliable Datagram）两种模式。RC提供面向连接、可靠的传输服务，适合于需要保证数据完整性的应用；UD则是无连接的，适合于低延迟、高吞吐量的应用。 3. **队列对（Queue Pair,QP）**：每个连接由一对队列构成，一个发送队列和一个接收队列，用于管理数据的发送和接收。 4. **verbs（ verbs）**：是InfiniBand编程模型的一部分，提供了一组API，允许应用程序直接控制网络操作，如发送、接收和管理队列对等。 5. **Service Level Agreement (SLA)**：InfiniBand支持多种服务质量级别，可以根据不同的应用需求设定优先级，确保关键任务的执行。 6. **错误检测与恢复**：协议包含了强大的错误检测和恢复机制，如CRC校验和路径恢复机制，保证了网络的稳定性和可靠性。 7. **Port and LID**：每个InfiniBand设备都有一个端口（Port）和逻辑标识符（LID），用于网络中的地址定位。 8. **RoCE (RDMA over Converged Ethernet)**：为了兼容以太网环境，InfiniBand引入了RoCE，允许在标准以太网上实现RDMA功能。 通过深入理解《InfiniBand协议 Vol 1-Release-1.4.pdf》这份文档，开发者和系统管理员可以更好地掌握InfiniBand技术，设计和优化高效的数据中心解决方案。它涵盖了协议的各个方面，包括协议格式、传输协议、队列管理、错误处理以及系统管理和配置等，是学习和实施InfiniBand技术的重要参考资料。

Infiniband Specification Vol 1-Release-1.4相关资料 （免积分） 内容包含 IB Specification Vol 1-Release-1.4-2020-04-07.pdf IB Specification Vol 2-Release-1.4-2020-04-07.pdf

NetAdvantage Ultimate 2012 Vol.1 注册码 授权码 破解版

Infragistics.NetAdvantage.for.Windows.Forms.2010 非常有名的win form控件 ,内含注册机,看不惯某些一个key还要10分的人

Windows XP SP2 VOL真正原版Windows XP SP2 VOL真正原版

ArchVizPRO Interior Vol.8 URP是一个在URP中制作的建筑可视化项目。这是一个完全可导航的现代公寓，包括一个带开放式厨房的客厅、休息区、两间卧室和两间浴室。从头开始构建每一个细节，这个室内有130多件家具和道具、自定义着色器和4K纹理。所有家具和道具都非常详细，可以在任何其他项目中重复使用。 产品特点： - 设施齐全的公寓 - 150多个预制件 - 细节层次 (LOD) - 包括电影动画 - CPU/GPU 渐进式就绪 - 高清 4K 纹理 - 后处理设置 - 自定义着色器图形着色器

comment copied from amazon 2001: I brought this book ( volume 2 also as well ) because of its " fame ", but when I read it, it has several draw backs. First, may be the original version is in German, so even with good translation, it seem does not fit in the usual English style we get used to. Also the topics it choose is too few and also the area covered is too narrow and not well co-ordinated. For example, the whole volume I is almost dedicated to Calculus of variation only. In volume 2, the whole book is dedicated to differential equations. But that is not the greatest drawback. The most bad point is that the book just presents formulae after formulae, equations after equations, without giving examples of how to use it, and also no exercise for me to practice.

mt4 vol 真实颜色应用于mt4的原来指标成交量显示和国内不一致的问题，原来的是成交量增加了就是绿色，减少了就是红色，相当不明显

Introduction This book describes the TCP/IP protocol suite, but from a different perspective than other texts on TCP/IP. Instead of just describing the protocols and what they do, we'll use a popular diagnostic tool to watch the protocols in action. Seeing how the protocols operate in varying circumstances provides a greater understanding of how they work and why certain design decisions were made. It also provides a look into the implementation of the protocols, without having to wade through thousands of lines of source code. When networking protocols were being developed in the 1960s through the 1980s, expensive, dedicated hardware was required to see the packets going "across the wire." Extreme familiarity with the protocols was also required to comprehend the packets displayed by the hardware. Functionality of the hardware analyzers was limited to that built in by the hardware designers. Today this has changed dramatically with the ability of the ubiquitous workstation to monitor a local area network Mogul 1990. Just attach a workstation to your network, run some publicly available software (described in Appendix A), and watch what goes by on the wire. While many people consider this a tool to be used for diagnosing network problems, it is also a powerful tool for understanding how the network protocols operate, which is the goal of this book. This book is intended for anyone wishing to understand how the TCP/IP protocols operate: programmers writing network applications, system administrators responsible for maintaining computer systems and networks utilizing TCP/IP, and users who deal with TCP/IP applications on a daily basis. Organization of the Book We take a bottom-up approach to the TCP/IP protocol suite. After providing a basic introduction to TCP/IP in Chapter 1, we will start at the link layer in Chapter 2 and work our way up the protocol stack. This provides the required background for later chapters for readers who aren't familiar with TCP/IP or networking in general. This book also uses a functional approach instead of following a strict bottom-to-top order. For example, Chapter 3 describes the IP layer and the IP header. But there are numerous fields in the IP header that are best described in the context of an application that uses or is affected by a particular field. Fragmentation, for example, is best understood in terms of UDP (Chapter 11), the protocol often affected by it. The time-to-live field is fully described when we look at the Traceroute program in Chapter 8, because this field is the basis for the operation of the program. Similarly, many features of ICMP are described in the later chapters, in terms of how a particular ICMP message is used by a protocol or an application. We also don't want to save all the good stuff until the end, so we describe TCP/IP applications as soon as we have the foundation to understand them. Ping and Traceroute are described after IP and ICMP have been discussed. The applications built on UDP (multicasting, the DNS, TFTP, and BOOTP) are described after UDP has been examined. The TCP applications, however, along with network management, must be saved until the end, after we've thoroughly described TCP. This text focuses on how these applications use the TCP/IP protocols. We do not provide all the details on running these applications. Readers This book is self-contained and assumes no specific knowledge of networking or TCP/IP. Numerous references are provided for readers interested in additional details on specific topics. This book can be used in many ways. It can be used as a self-study reference and covered from start to finish by someone interested in all the details on the TCP/IP protocol suite. Readers with some TCP/IP background might want to skip ahead and start with Chapter 7, and then focus on the specific chapters in which they're interested. Exercises are provided at the end of the chapters, and most solutions are in Appendix D. This is to maximize the usefulness of the text as a self-study reference. When used as part of a one- or two-semester course in computer networking, the focus should be on IP (Chapters 3 and 9), UDP (Chapter 11), and TCP (Chapters 17-24), along with some of the application chapters. Many forward and backward references are provided throughout the text, along with a thorough index, to allow individual chapters to be studied by themselves. A list of all the acronyms used throughout the text, along with the compound term for the acronym, appears on the inside back covers. If you have access to a network you are encouraged to obtain the software used in this book (Appendix F) and experiment on your own. Hands-on experimentation with the protocols will provide the greatest knowledge (and make it more fun). Systems Used for Testing Every example in the book was run on an actual network and the resulting output saved in a file for inclusion in the text. Figure 1.11 (p. 18) shows a diagram of the different hosts, routers, and networks that are used. (This figure is also duplicated on the inside front cover for easy reference while reading the book.) This collection of networks is simple enough that the topology doesn't confuse the examples, and with four systems acting as routers, we can see the error messages generated by routers. Most of the systems have a name that indicates the type of software being used: bsdi, svr4, sun, solaris, aix, slip, and so on. In this way we can identify the type of software that we're dealing with by looking at the system name in the printed output. A wide range of different operating systems and TCP/IP implementations are used: BSD/386 Version 1.0 from Berkeley Software Design, Inc., on the hosts named bsdi and slip. This system is derived from the BSD Networking Software, Release 2.0. (We show the lineage of the various BSD releases in Figure 1.10 on p. 17.) Unix System V/386 Release 4.0 Version 2.0 from U.H. Corporation, on the host named svr4. This is vanilla SVR4 and contains the standard implementation of TCP/IP from Lachman Associates used with most versions of SVR4. SunOS 4.1.3 from Sun Microsystems, on the host named sun. The SunOS 4.1.x systems are probably the most widely used TCP/IP implementations. The TCP/IP code is derived from 4.2BSD and 4.3BSD. Solaris 2.2 from Sun Microsystems, on the host named solaris. The Solaris 2.x systems have a different implementation of TCP/IP from the earlier SunOS 4.1.x systems, and from SVR4. (This operating system is really SunOS 5.2, but is commonly called Solaris 2.2.) AIX 3.2.2 from IBM on the host named aix. The TCP/IP implementation is based on the 4.3BSD Reno release. 4.4BSD from the Computer Systems Research Group at the University of California at Berkeley, on the host vangogh.cs.berkeley.edu. This system has the latest release of TCP/IP from Berkeley. (This system isn't shown in the figure on the inside front cover, but is reachable across the Internet.) Although these are all Unix systems, TCP/IP is operating system independent, and is available on almost every popular non-Unix system. Most of this text also applies to these non-Unix implementations, although some programs (such as Traceroute) may not be provided on all systems. Typographical Conventions When we display interactive input and output we'll show our typed input in a bold font, and the computer output like this. Comments are added in italics. Also, we always include the name of the system as part of the shell prompt (bsdi in this example) to show on which host the command was run. Throughout the text we'll use indented, parenthetical notes such as this to describe historical points or implementation details. We sometimes refer to the complete description of a command in the Unix manual as in ifconfig(8). This notation, the name of the command followed by a number in parentheses, is the normal way of referring to Unix commands. The number in parentheses is the section number in the Unix manual of the "manual page" for the command, where additional information can be located. Unfortunately not all Unix systems organize their manuals the same, with regard to the section numbers used for various groupings of commands. We'll use the BSD-style section numbers (which is the same for BSD-derived systems such as SunOS 4.1.3), but your manuals may be organized differently. Acknowledgments Although the author's name is the only one to appear on the cover, the combined effort of many people is required to produce a quality text book. First and foremost is the author's family, who put up with the long and weird hours that go into writing a book. Thank you once again, Sally, Bill, Ellen, and David. The consulting editor, Brian Kernighan, is undoubtedly the best in the busin...

这本是是ROS by example vol 2.是在第一册的基础上进行的改版。