What are the relevant differences between Asynchronous (ATS) and Credit Based...RealTime-at-Work (RTaW)
?
This document discusses shaping techniques for time-sensitive networking, specifically asynchronous traffic shaping (ATS) and credit-based shaping (CBS). It provides details on the scheduling rules, algorithms, and behavior of ATS and CBS. It also compares their similarities and differences, such as how they handle lower and higher priority interference and scheduling of smaller frames. An example network topology is presented to illustrate the different effects of ATS versus CBS with bursty incoming traffic. The document aims to explain the relevant aspects of these shaping techniques.
The document discusses the ARM Trusted Firmware, specifically focusing on the BL31 component and its usage, including boot management and power management for Zynq UltraScale+ MPSoC. It outlines the structure of the firmware, describes the roles of various firmware layers, and provides instructions on how to configure and use the BL31 standalone. The document also includes links to resources and source code for further exploration of the ARM Trusted Firmware.
ZynqMPのブートとパワーマネージメント : (ZynqMP Boot and Power Management)Mr. Vengineer
?
2016年2月20日(金)のZynq Ultrasclae+ MPSoC 勉強会で使った資料です。
追記) 2016.05.08
公式ARM Trusted Firmwareのサイトに、Zynq UltraScale+ MPSoCの実装が追加されていていることを明記した
This is the material I used at Zynq Ultrasclae + MPSoC SIG on 20th February (Friday).
Addendum) 2016.05.08
We stated that the implementation of Zynq UltraScale + MPSoC was added to the official ARM Trusted Firmware site.
This document discusses VPC by default and AWS services. It provides examples of how EC2 and S3 can communicate through a VPC using security groups and NACLs. It also discusses using VPC for hybrid use cases with on-premise systems through IPsec VPN or Direct Connect. Finally, it highlights how VPC allows integration between different AWS services.
The document discusses the ARM Trusted Firmware, specifically focusing on the BL31 component and its usage, including boot management and power management for Zynq UltraScale+ MPSoC. It outlines the structure of the firmware, describes the roles of various firmware layers, and provides instructions on how to configure and use the BL31 standalone. The document also includes links to resources and source code for further exploration of the ARM Trusted Firmware.
ZynqMPのブートとパワーマネージメント : (ZynqMP Boot and Power Management)Mr. Vengineer
?
2016年2月20日(金)のZynq Ultrasclae+ MPSoC 勉強会で使った資料です。
追記) 2016.05.08
公式ARM Trusted Firmwareのサイトに、Zynq UltraScale+ MPSoCの実装が追加されていていることを明記した
This is the material I used at Zynq Ultrasclae + MPSoC SIG on 20th February (Friday).
Addendum) 2016.05.08
We stated that the implementation of Zynq UltraScale + MPSoC was added to the official ARM Trusted Firmware site.
This document discusses VPC by default and AWS services. It provides examples of how EC2 and S3 can communicate through a VPC using security groups and NACLs. It also discusses using VPC for hybrid use cases with on-premise systems through IPsec VPN or Direct Connect. Finally, it highlights how VPC allows integration between different AWS services.
VyOS now supports VXLAN interfaces which allow multiple L2 segments to be multiplexed over a single physical network. VXLAN uses encapsulation to transport Ethernet frames over IP. The VNI field in VXLAN headers maps frames to different L2 segments. VyOS VXLAN interfaces can be configured and used like physical interfaces for routing, bridging, and protocols like OSPF. However, attributes like the VNI and multicast group cannot be changed after interface creation without deleting and recreating the interface.
This document discusses how FreakOut uses AWS for its real-time bidding advertising business. It needs low latency to process bids within 50ms. While AWS can provide the necessary scalability and flexibility, the author found latency to occasionally be significantly higher in AWS compared to their own data centers. The document suggests ways AWS could improve, such as providing placement groups for latency in addition to bandwidth and a playback feature to generate CLI commands from the console. It also stresses the importance of testing infrastructure changes to avoid bugs that could destroy systems.
This document summarizes case studies of using VyOS in Kauli's supply-side platform (SSP). It discusses:
1) How VyOS is used as the default gateway router for all of Kauli's servers, handling up to 400 million ads per day. Peak traffic graphs show the load on the VyOS router.
2) Techniques for scaling the VyOS implementation, such as using OSPF/ECMP routing after adding more VyOS routers.
3) Tuning tips for optimizing VyOS performance, including settings for NUMA, NAPI, buffer sizes, CPU affinity, and conntrack tables.
4) How microburst traffic patterns can cause
This document discusses results from using the dig command with the +nsid option to analyze Amazon Route 53. The document contains the following information:
(1) An agenda outlining what will be analyzed about Route 53 including the number of name servers (NS), IP addresses, edge locations, name server IDs (NSIDs) for individual NS, and unique NSIDs observed.
(2) Results showing there are 2048 NS distributed across the top level domains .com, .net, .org, and .co.uk with 512 NS each. There are also around 80 edge locations.
(3) Findings that a single NS/IP address can return multiple NSIDs depending on the query location, due
The document discusses Route53 domain name management in AWS. It describes how "parent-child domains" refer to multiple related domain names that are subsets of each other, such as example.jp, sub.example.jp, and foo.bar.sub.example.jp. The key concept discussed is "parent-child cohabitation", which occurs when the name servers of parent and child domains partially overlap, meaning the domains share the same physical server resources. The author experimented with creating many related hosted zones in Route53 but was unable to deliberately cause parent-child cohabitation.
Este documento describe cómo funcionan los filtros de captura (CaptureFilter) en Wireshark y tcpdump. Explica que los filtros de captura se implementan usando BPF (Berkeley Packet Filter) para filtrar paquetes de forma eficiente directamente en el kernel. Luego proporciona ejemplos de código BPF generado para diferentes tipos comunes de filtros como "ip", "port 80", e "ip and port 80", mostrando cómo verifican los encabezados para determinar si un paquete debe capturarse. Finalmente, incluye referencias a los encabezados
Protect Your IoT Data with UbiBot's Private Platform.pptxユビボット 株式会社
?
Our on-premise IoT platform offers a secure and scalable solution for businesses, with features such as real-time monitoring, customizable alerts and open API support, and can be deployed on your own servers to ensure complete data privacy and control.
2. Measurement of
Maximum new NAT-sessions
per second
(How to send packets)
2014/11/02
#vyosjp
@otsuka752 (@twovs)
3. about me
? @otsuka752 (@twovs)
? ネコ2人+奥さん+可愛い娘
?? 無線LLAANN装置の開発((11999999~~22000044))
? オンラインゲームのシステム管理者(2004~)
? ただし,ゲームには全く興味無し
? ZFS 最高!!! beadm 便利!!!
4. はじめに/Intro
? VyOS は10万セッションのNAT も動くらしい
VyOS can store 100K sessions and works well
http://research.ssaakkuurraa..aadd..jjpp//
2012/07/24/janog30-network2/
? 単位時間あたりの新規session 数は?
How many new sessions/sec does VyOS handle?
6. 構成/System
(*1) Guest properties (VyOS)
CPU x1
Memory 2GB
((**22)) IICCMMPP((たくさんのSSrrcc//DDsstt IIPPAAddddrr の組合せ))
ICMP(Many kinds of Src/Dst IPAddr pairs)
(*3) Host properties
CPU AMD Athlon 64 X2 Dual Core Processor 6400+
Memory 8GB
OS Solaris 11.1
VirtualBox 4.3.14
7. 設定/Configuration
? IPAddr と下記以外はデフォルト値
Use Default Configuration
except for IPAddr and below
set protocols static route 0.0.0.0/0 next-hop ‘(server)'
set nat source rule 10 outbound-interface 'eth1'
set nat source rule 10 source address '0.0.0.0/0'
set nat source rule 10 translation address 'masquerade'
set system conntrack expect-table-size '2048'
set system conntrack hash-size '16384'
set system conntrack table-size '1048576'
8. 試験手順/Testing procedure
(1) VyOS のNAT セッションやカウンタをリセット
Reset conntrack and clear NAT counters of VyOS
vvyyooss@@vvyyooss::~~$$ rreesseett ccoonnnnttrraacckk
This will clear all currently tracked and expected
connections. Continue? (Y/N) [N]: y
vyos@vyos:~$ clear nat source counters
9. 試験手順/Testing procedure
(2) クライアントからP[pps] でN 種類のパケットを送信
Send N different kinds of packets to VyOS at P[pps]
from client
[client]$ scapy
Welcome to Scapy (2.2.0-1)
>>>
Scapy も良いけど…
Scapy is good.
10. 試験手順/Testing procedure
(2) クライアントからP[pps] でN 種類のパケットを送信
Send N different kinds of packets to VyOS at P[pps]
from client
[client]$ sudo tcpreplay --unique-ip ?
-l ${N} --pps=${P} -K -i eth0 file.pcap
Tcpreplay もイイネ
I love Tcpreplay too.
11. 試験手順/Testing procedure
(3) サーバに届いたパケット数を数える
Count the number of packets from client
[[sseerrvveerr]]$$ ssuuddoo ttccppdduummpp --nn --ii eetthh00
12. 試験手順/Testing procedure
(4) VyOS でNAT table の数を見る
Show NAT statistics on VyOS
vyos@vyos:~$ show nat source statistics
rule pkts bytes interface
---- ---- ----- ---------
10 100K 2800K eth1
16. 備考/Notes
? >30K[pps] のパケロス発生時でも
[サーバに届いたパケット数] と
[VyOS で作られたNAT session 数] は概ね同数
>30K[pps] condition, i.e. PER != 0
[number of packets received by server]
is also nearly equal to
[number of NAT-sessions on VyOS]
21. お知らせ
? 日本語サイト始めてみました!
? http://tcpreplay.jp/
? https://github.com/otsuka752/
? Web site in English
? http://tcpreplay.appneta.com/
? https://github.com/appneta/tcpreplay/