 Cilium v1.11 Documentationcom/cilium/cilium-cli/main/stable- v0.14.txt) CLI_ARCH=amd64 if [ "$(uname -m)" = "aarch64" ]; then CLI_ARCH=arm64; fi curl -L --fail --remote-name-all https://github.com/cilium/cilium- cli/releases/download/${C githubusercontent.com/cilium/cilium-cli/main/stable- v0.14.txt) CLI_ARCH=amd64 if [ "$(uname -m)" = "arm64" ]; then CLI_ARCH=arm64; fi curl -L --fail --remote-name-all https://github.com/cilium/cilium- cli/releases/ com/cilium/cilium-cli/main/stable- v0.14.txt) CLI_ARCH=amd64 if [ "$(uname -m)" = "aarch64" ]; then CLI_ARCH=arm64; fi curl -L --fail --remote-name-all https://github.com/cilium/cilium- cli/releases/download/${C0 码力 | 1373 页 | 19.37 MB | 1 年前3 Cilium v1.11 Documentationcom/cilium/cilium-cli/main/stable- v0.14.txt) CLI_ARCH=amd64 if [ "$(uname -m)" = "aarch64" ]; then CLI_ARCH=arm64; fi curl -L --fail --remote-name-all https://github.com/cilium/cilium- cli/releases/download/${C githubusercontent.com/cilium/cilium-cli/main/stable- v0.14.txt) CLI_ARCH=amd64 if [ "$(uname -m)" = "arm64" ]; then CLI_ARCH=arm64; fi curl -L --fail --remote-name-all https://github.com/cilium/cilium- cli/releases/ com/cilium/cilium-cli/main/stable- v0.14.txt) CLI_ARCH=amd64 if [ "$(uname -m)" = "aarch64" ]; then CLI_ARCH=arm64; fi curl -L --fail --remote-name-all https://github.com/cilium/cilium- cli/releases/download/${C0 码力 | 1373 页 | 19.37 MB | 1 年前3
 PyArmor Documentation v6.2.7compatible. For example, try to obfuscate the scripts with --platform linux.arm.0 in Windows: pyarmor obfuscate --platform linux.arm.0 foo.py Because the default platform is full features windows.x86_64.7 reboot with platform windows.x86_64.0, then obfuscate the script for this low feature platform linux.arm.0. It also could be set the enviornment variable PYARMOR_PLATFORM to same feature platform as target ws.x86_64.0 pyarmor obfuscate --platform linux.arm.0 foo.py # In Windows set PYARMOR_PLATFORM=windows.x86_64.0 pyarmor obfuscate --platform linux.arm.0 foo.py set PYARMOR_PLATFORM= Running Obfuscated0 码力 | 159 页 | 123.91 KB | 1 年前3 PyArmor Documentation v6.2.7compatible. For example, try to obfuscate the scripts with --platform linux.arm.0 in Windows: pyarmor obfuscate --platform linux.arm.0 foo.py Because the default platform is full features windows.x86_64.7 reboot with platform windows.x86_64.0, then obfuscate the script for this low feature platform linux.arm.0. It also could be set the enviornment variable PYARMOR_PLATFORM to same feature platform as target ws.x86_64.0 pyarmor obfuscate --platform linux.arm.0 foo.py # In Windows set PYARMOR_PLATFORM=windows.x86_64.0 pyarmor obfuscate --platform linux.arm.0 foo.py set PYARMOR_PLATFORM= Running Obfuscated0 码力 | 159 页 | 123.91 KB | 1 年前3
 PyArmor Documentation v6.3.1compatible. For example, try to obfuscate the scripts with --platform linux.arm.0 in Windows: pyarmor obfuscate --platform linux.arm.0 foo.py Because the default platform is full features windows.x86_64.7 reboot with platform windows.x86_64.0, then obfuscate the script for this low feature platform linux.arm.0. It also could be set the enviornment variable PYARMOR_PLATFORM to same feature platform as target ws.x86_64.0 pyarmor obfuscate --platform linux.arm.0 foo.py # In Windows set PYARMOR_PLATFORM=windows.x86_64.0 pyarmor obfuscate --platform linux.arm.0 foo.py set PYARMOR_PLATFORM= Running Obfuscated0 码力 | 161 页 | 124.89 KB | 1 年前3 PyArmor Documentation v6.3.1compatible. For example, try to obfuscate the scripts with --platform linux.arm.0 in Windows: pyarmor obfuscate --platform linux.arm.0 foo.py Because the default platform is full features windows.x86_64.7 reboot with platform windows.x86_64.0, then obfuscate the script for this low feature platform linux.arm.0. It also could be set the enviornment variable PYARMOR_PLATFORM to same feature platform as target ws.x86_64.0 pyarmor obfuscate --platform linux.arm.0 foo.py # In Windows set PYARMOR_PLATFORM=windows.x86_64.0 pyarmor obfuscate --platform linux.arm.0 foo.py set PYARMOR_PLATFORM= Running Obfuscated0 码力 | 161 页 | 124.89 KB | 1 年前3
 BAETYL 1.0.0 Documentationconsistent. In addition, Baetyl also isolates and limits the resources of containers, and allocates the CPU, memory and other resources of each running instance accurately to improve the efficiency of resource Support multiple platforms: Baetyl supports multiple hardware and software platforms, such as X86 and ARM CPU, Linux and Darwin operating systems. Components As an edge computing platform, Baetyl not only mapped according to the Devices information, and the resources that the containers can use, such as CPU, memory, etc., are configured according to the Resources information. Services can be accessed directly0 码力 | 135 页 | 15.44 MB | 1 年前3 BAETYL 1.0.0 Documentationconsistent. In addition, Baetyl also isolates and limits the resources of containers, and allocates the CPU, memory and other resources of each running instance accurately to improve the efficiency of resource Support multiple platforms: Baetyl supports multiple hardware and software platforms, such as X86 and ARM CPU, Linux and Darwin operating systems. Components As an edge computing platform, Baetyl not only mapped according to the Devices information, and the resources that the containers can use, such as CPU, memory, etc., are configured according to the Resources information. Services can be accessed directly0 码力 | 135 页 | 15.44 MB | 1 年前3
 Cilium v1.5 Documentationin-kernel verifier ensures that BPF programs are safe to run and a JIT compiler converts the bytecode to CPU architecture specific instruc�ons for na�ve execu�on efficiency. BPF programs can be run at various between 10 seconds and 30 minutes or 12 hours for LRU based maps. This should automa�cally op�mize CPU consump�on as much as possible while keeping the connec�on tracking table u�liza�on below 25%. If needed and bpf-ct-global-tcp-max can be increased. Se�ng both of these op�ons will be a trade-off of CPU for conntrack-gc-interval , and for bpf-ct-global-any-max and bpf-ct-global-tcp-max the amount of0 码力 | 740 页 | 12.52 MB | 1 年前3 Cilium v1.5 Documentationin-kernel verifier ensures that BPF programs are safe to run and a JIT compiler converts the bytecode to CPU architecture specific instruc�ons for na�ve execu�on efficiency. BPF programs can be run at various between 10 seconds and 30 minutes or 12 hours for LRU based maps. This should automa�cally op�mize CPU consump�on as much as possible while keeping the connec�on tracking table u�liza�on below 25%. If needed and bpf-ct-global-tcp-max can be increased. Se�ng both of these op�ons will be a trade-off of CPU for conntrack-gc-interval , and for bpf-ct-global-any-max and bpf-ct-global-tcp-max the amount of0 码力 | 740 页 | 12.52 MB | 1 年前3
 Cilium v1.10 Documentationresource-constrained, remote locations or inside IoT appliances. Cilium is presently supported on amd64 and arm64 architectures. Install a Master Node The first step is to install a K3s master node making sure istioctl-1.10.4-linux-amd64.tar.gz | tar xz Linux (arm64) curl -L https://github.com/cilium/istio/releases/download/1.10.4/cilium- istioctl-1.10.4-linux-arm64.tar.gz | tar xz OSX curl -L https://github Silicon) curl -L https://github.com/cilium/istio/releases/download/1.10.4/cilium- istioctl-1.10.4-osx-arm64.tar.gz | tar xz Note Cilium integration, as presented in this Getting Started Guide, has been tested0 码力 | 1307 页 | 19.26 MB | 1 年前3 Cilium v1.10 Documentationresource-constrained, remote locations or inside IoT appliances. Cilium is presently supported on amd64 and arm64 architectures. Install a Master Node The first step is to install a K3s master node making sure istioctl-1.10.4-linux-amd64.tar.gz | tar xz Linux (arm64) curl -L https://github.com/cilium/istio/releases/download/1.10.4/cilium- istioctl-1.10.4-linux-arm64.tar.gz | tar xz OSX curl -L https://github Silicon) curl -L https://github.com/cilium/istio/releases/download/1.10.4/cilium- istioctl-1.10.4-osx-arm64.tar.gz | tar xz Note Cilium integration, as presented in this Getting Started Guide, has been tested0 码力 | 1307 页 | 19.26 MB | 1 年前3
 Cilium v1.6 Documentation\ --min-cpu-platform "Intel Broadwell" \ kata-testing gcloud compute ssh kata-testing # While ssh'd into the VM: $ [ -z "$(lscpu|grep GenuineIntel)" ] && { echo "ERROR: Need an Intel CPU"; exit 1; kernel verifier ensures that BPF programs are safe to run and a JIT compiler converts the bytecode to CPU architecture specific instructions for native execution efficiency. BPF programs can be run at various BPF datapath to perform more aggressive aggregation on packet forwarding related events to reduce CPU consumption while running cilium monitor. The automatic change only applies to the default ConfigMap0 码力 | 734 页 | 11.45 MB | 1 年前3 Cilium v1.6 Documentation\ --min-cpu-platform "Intel Broadwell" \ kata-testing gcloud compute ssh kata-testing # While ssh'd into the VM: $ [ -z "$(lscpu|grep GenuineIntel)" ] && { echo "ERROR: Need an Intel CPU"; exit 1; kernel verifier ensures that BPF programs are safe to run and a JIT compiler converts the bytecode to CPU architecture specific instructions for native execution efficiency. BPF programs can be run at various BPF datapath to perform more aggressive aggregation on packet forwarding related events to reduce CPU consumption while running cilium monitor. The automatic change only applies to the default ConfigMap0 码力 | 734 页 | 11.45 MB | 1 年前3
 Cilium v1.8 Documentationassumes installation on amd64 architecture. Cilium is presently supported on amd64 architecture with ARM support planned [https://github.com/cilium/cilium/issues/9898] for a future release. Install a Master istioctl version 1.10.4 [https://github.com/cilium/istio/releases/tag/1.10.4]: Linux (amd64) Linux (arm64) OSX OSX (Apple Silicon) curl -L https://github.com/cilium/istio/releases/download/1.10.4/cilium- xz curl -L https://github.com/cilium/istio/releases/download/1.10.4/cilium- istioctl-1.10.4-linux-arm64.tar.gz | tar xz curl -L https://github.com/cilium/istio/releases/download/1.10.4/cilium- istioctl-10 码力 | 1124 页 | 21.33 MB | 1 年前3 Cilium v1.8 Documentationassumes installation on amd64 architecture. Cilium is presently supported on amd64 architecture with ARM support planned [https://github.com/cilium/cilium/issues/9898] for a future release. Install a Master istioctl version 1.10.4 [https://github.com/cilium/istio/releases/tag/1.10.4]: Linux (amd64) Linux (arm64) OSX OSX (Apple Silicon) curl -L https://github.com/cilium/istio/releases/download/1.10.4/cilium- xz curl -L https://github.com/cilium/istio/releases/download/1.10.4/cilium- istioctl-1.10.4-linux-arm64.tar.gz | tar xz curl -L https://github.com/cilium/istio/releases/download/1.10.4/cilium- istioctl-10 码力 | 1124 页 | 21.33 MB | 1 年前3
 Cilium v1.7 Documentationassumes installation on amd64 architecture. Cilium is presently supported on amd64 architecture with ARM support planned [https://github.com/cilium/cilium/issues/9898] for a future release. Install a Master kernel verifier ensures that BPF programs are safe to run and a JIT compiler converts the bytecode to CPU architecture specific instructions for native execution efficiency. BPF programs can be run at various BPF datapath to perform more aggressive aggregation on packet forwarding related events to reduce CPU consumption while running cilium monitor. The automatic change only applies to the default ConfigMap0 码力 | 885 页 | 12.41 MB | 1 年前3 Cilium v1.7 Documentationassumes installation on amd64 architecture. Cilium is presently supported on amd64 architecture with ARM support planned [https://github.com/cilium/cilium/issues/9898] for a future release. Install a Master kernel verifier ensures that BPF programs are safe to run and a JIT compiler converts the bytecode to CPU architecture specific instructions for native execution efficiency. BPF programs can be run at various BPF datapath to perform more aggressive aggregation on packet forwarding related events to reduce CPU consumption while running cilium monitor. The automatic change only applies to the default ConfigMap0 码力 | 885 页 | 12.41 MB | 1 年前3
 BAETYL 0.1.6 Documentationconsistent. In addition, Baetyl also isolates and limits the resources of containers, and allocates the CPU, memory and other resources of each running instance accurately to improve the efficiency of resource Support multiple platforms: Baetyl supports multiple hardware and software platforms, such as X86 and ARM CPU, Linux and Darwin operating systems. Components As an edge computing platform, Baetyl not only mapped according to the Devices information, and the resources that the containers can use, such as CPU, memory, etc., are configured according to the Resources information. Services can be accessed directly0 码力 | 119 页 | 11.46 MB | 1 年前3 BAETYL 0.1.6 Documentationconsistent. In addition, Baetyl also isolates and limits the resources of containers, and allocates the CPU, memory and other resources of each running instance accurately to improve the efficiency of resource Support multiple platforms: Baetyl supports multiple hardware and software platforms, such as X86 and ARM CPU, Linux and Darwin operating systems. Components As an edge computing platform, Baetyl not only mapped according to the Devices information, and the resources that the containers can use, such as CPU, memory, etc., are configured according to the Resources information. Services can be accessed directly0 码力 | 119 页 | 11.46 MB | 1 年前3
共 417 条
- 1
- 2
- 3
- 4
- 5
- 6
- 42














