Linux就该这么学 第2版因此用户不能直接访问内核。虽然通过调用系统提供的 API(应用程序编程接口)就能实现 某个功能,但哪怕实现“将一条信息通过互联网传输给别人”这样简单的任务,都要手动调 新手必须掌握的 Linux 命令 66 用几十次 API 接口,使用起来太不切实际。而最外层的服务程序则是最贴近于用户端的,这 些服务程序是集成了大量 API 接口的完整软件,微信、QQ 就是这样的服务程序。 易、腾讯等门户网站的青睐。本书将在第 20 章讲解 Nginx 服务程序。 Apache 程序是目前拥有很高市场占有率的 Web 服务程序之一,其跨平台和安全性广泛被 认可且拥有快速、可靠、简单的 API 扩展。图 10-2 所示为 Apache 服务基金会的著名 Logo, 它的名字取自美国印第安人的土著语,寓意为“拥有高超的作战策略和无穷的耐性”。Apache 服务程序可以运行在 Linux httpd_can_connect_ftp --> off httpd_can_connect_ldap --> off httpd_can_connect_mythtv --> off httpd_can_connect_zabbix --> off httpd_can_network_connect --> off httpd_can_network_connect_cobbler --> off httpd_can_network_connect_db0 码力 | 552 页 | 22.25 MB | 1 年前3
Cilium v1.10 Documentationtechnical deep dive of eBPF and XDP technology, primarily focused at developers. API Reference : Details the Cilium agent API for interacting with a local Cilium instance. Development Guide : Gives background Podcasts Blog posts Books Talks Further Documents API Reference Introduction How to access the API CLI Client Golang Package Compatibility Guarantees API Reference Internals Hubble internals Hubble clusters. Create a Service Principal: In order to allow cilium-operator to interact with the Azure API, a Service Principal with Contributor privileges over the AKS cluster is required (see Azure IPAM required0 码力 | 1307 页 | 19.26 MB | 1 年前3
Cilium v1.8 Documentationtechnical deep dive of BPF and XDP technology, primarily focused at developers. API Reference : Details the Cilium agent API for interacting with a local Cilium instance. Development Guide : Gives background Podcasts Blog posts Books Talks Further Documents API Reference Introduction How to access the API CLI Client Golang Package Compatibility Guarantees API Reference Hubble internals Hubble Architecture contact k8s api-server In the Cilum agent logs you will see: level=info msg="Establishing connection to apiserver" host="https://10.96.0.1:443" subsys=k8s level=error msg="Unable to contact k8s api-server"0 码力 | 1124 页 | 21.33 MB | 1 年前3
Cilium v1.9 Documentationtechnical deep dive of eBPF and XDP technology, primarily focused at developers. API Reference : Details the Cilium agent API for interacting with a local Cilium instance. Development Guide : Gives background Podcasts Blog posts Books Talks Further Documents API Reference Introduction How to access the API CLI Client Golang Package Compatibility Guarantees API Reference Hubble internals Hubble Architecture contact k8s api-server In the Cilum agent logs you will see: level=info msg="Establishing connection to apiserver" host="https://10.96.0.1:443" subsys=k8s level=error msg="Unable to contact k8s api-server"0 码力 | 1263 页 | 18.62 MB | 1 年前3
Cilium v1.7 Documentationtechnical deep dive of BPF and XDP technology, primarily focused at developers. API Reference : Details the Cilium agent API for interacting with a local Cilium instance. Getting Started : Gives background 4 Examples Layer 7 Examples Kubernetes Endpoint Lifecycle Troubleshooting L7 Protocol Visibility API Rate Limiting Default Rate Limits Configuration Automatic Adjustment Metrics Understanding the log Podcasts Blog posts Books Talks Further Documents API Reference Introduction How to access the API CLI Client Golang Package Compatibility Guarantees API Reference Reference Command Cheatsheet Command0 码力 | 885 页 | 12.41 MB | 1 年前3
Cilium v1.11 Documentationtechnical deep dive of eBPF and XDP technology, primarily focused at developers. API Reference : Details the Cilium agent API for interacting with a local Cilium instance. Development Guide : Gives background Podcasts Blog posts Books Talks Further Documents API Reference Introduction How to access the API CLI Client Golang Package Compatibility Guarantees API Reference Internals Hubble internals Hubble clusters. Create a Service Principal: In order to allow cilium-operator to interact with the Azure API, a Service Principal with Contributor privileges over the AKS cluster is required (see Azure IPAM required0 码力 | 1373 页 | 19.37 MB | 1 年前3
Cilium v1.6 Documentationtechnical deep dive of BPF and XDP technology, primarily focused at developers. API Reference : Details the Cilium agent API for interacting with a local Cilium instance. Developer / Contributor Guide : Guide BPF Architecture Toolchain Program Types Further Reading API Reference Introduction How to access the API Compatibility Guarantees API Reference Reference Command Cheatsheet Command utilities: Self-Managed Kubernetes Managed Kubernetes Installer Integrations CNI Chaining Security Tutorials HTTP/REST API call authorization Locking down external access with DNS-based policies Securing a Kafka cluster How0 码力 | 734 页 | 11.45 MB | 1 年前3
Cilium v1.5 Documentationtechnical deep dive of BPF and XDP technology, primarily focused at developers. API Reference : Details the Cilium agent API for interac�ng with a local Cilium instance. Developer / Contributor Guide : Guide BPF Architecture Toolchain Program Types Further Reading API Reference Introduc�on How to access the API Compa�bility Guarantees API Reference Reference Command Cheatsheet Command u�li�es: Command MicroK8s Self-Managed Kubernetes Managed Kubernetes Installer Integra�ons Security Tutorials HTTP/REST API call authoriza�on Locking down external access with DNS-based policies Securing a Ka�a cluster How0 码力 | 740 页 | 12.52 MB | 1 年前3
openEuler 23.09 技术白皮书Management),提供了异构内存互联的中心化管理机制,且 GMEM API 与 Linux 原生内存管理 API 保持统一,易用性强,性能与可移植性好。 加速器使用 GMEM API 将内存接入统一地址空间后,可自动获得 GMEM 面向异构内存编程优化的能力。与此同时,加 速器驱动无需重复实现内存管理框架,大幅降低开发维护带来的成本。 开发者使用一套统一申请、释放的 API,即可完成异构内存编程,无需处理内存搬移等细节。在加速器 r 内存消息交互框架提供了设备接入抽象层。在统一的地址空间下,GMEM 可以在数据需要被访问或换页时,自动地迁移数 据到 OS 或加速器端。 功能描述 Host Device GMEM API Process Main Remote Pager GMEM( 异构内存 ) GMEM Remote Pager GMEM( 异构内存 ) Co-process 统一虚拟地址空间 mmap/hmadvise 机与加速器进行搬移。在实际使用时,加速器可在内存不足时可以借用主机内存,同时回收加速器内的冷内存,达到内存 超分的效果,突破模型参数受限于加速器内存的限制,实现低成本的大模型训练。 通过在内核中提供 GMEM 高层 API,允许加速器驱动通过注册 GMEM 规范所定义的 MMU 函数直接获取内存管理功能, 建立逻辑页表并进行内存超分。逻辑页表将内存管理的高层逻辑与 CPU 的硬件相关层解耦,从而抽象出能让各类加速器复0 码力 | 52 页 | 5.25 MB | 1 年前3
openEuler OS Technical Whitepaper
Innovation Projects
(June, 2023)unified management of both containers and node OS through Kubernetes, including atomic upgrades and API-based operations. Challenges In cloud-native scenarios, containers and Kubernetes are widely used status before the OS changes to implement collaborative scheduling of service containers and OSs. • API O&M: Kubernetes-native declarative APIs are used to manage and maintain OSs in a standard manner. devices, especially for devices that have certain restrictions on power consumption. • Difficult API adaptation: There are no unified APIs that mask differences in underlying hardware and networking,0 码力 | 116 页 | 3.16 MB | 1 年前3
共 44 条
- 1
- 2
- 3
- 4
- 5













