Home
last modified time | relevance | path

Searched refs:DSA (Results 1 – 25 of 43) sorted by relevance

12

/linux/Documentation/translations/zh_CN/networking/
H A Dtimestamping.rst554 3.2.1 DSA（分布式交换架构）交换机
558 执行端口多路复用或可选转发加速功能。每个 DSA 交换机端口在用户看来都是独立的
562 当 DSA 交换机连接到主机端口时，PTP 同步必须受到限制，因为交换机的可变排队
563 延迟引入了主机端口与其 PTP 伙伴之间的路径延迟抖动。因此，一些 DSA 交换机
565 仅测量线缆和 PHY 传播延迟。支持 Linux 的 DSA 交换机暴露了与任何其他网络
566 接口相同的 ABI（除了 DSA 接口在网络 I/O 方面实际上是虚拟的，它们确实有自
567 己的PHC）。典型地，但不是强制性地，所有DSA 交换机接口共享相同的 PHC。
569 通过设计，DSA 交换机对连接到其主机端口的 PTP 时间戳不需要任何特殊的驱动程
570 序处理。然而，当主机端口也支持 PTP 时间戳时，DSA 将负责拦截
572 SO_TIMESTAMPING API 不允许为同一数据包传递多个硬件时间戳，因此除了 DSA
[all …]
/linux/Documentation/networking/dsa/
H A Dconfiguration.rst4 DSA switch configuration from userspace
7 The DSA switch configuration is not integrated into the main userspace
15 To configure a DSA switch a couple of commands need to be executed. In this
32 Through DSA every port of a switch is handled like a normal linux Ethernet
42 - when a DSA user interface is brought up, the conduit interface is
44 - when the conduit interface is brought down, all DSA user interfaces are
88 DSA switches. These switches are capable to tag incoming and outgoing traffic
302 The existing DSA switches do not have the necessary hardware support to keep
308 Up until kernel v4.14, DSA only supported user space management of bridge FDB
319 Due to a bug, the bridge bypass FDB implementation provided by DSA did not
[all …]
H A Ddsa.rst5 This document describes the **Distributed Switch Architecture (DSA)** subsystem
23 or more CPU or management ports. The DSA subsystem currently relies on the
28 be later referred to as "conduit" and "cpu" in DSA terminology and code.
30 The D in DSA stands for Distributed, because the subsystem has been designed
33 ports are referred to as "dsa" ports in DSA terminology and code. A collection
36 For each front-panel port, DSA creates specialized network devices which are
39 interfaces in DSA terminology and code.
41 The ideal case for using DSA is when an Ethernet switch supports a "switch tag"
54 Note that DSA does not currently create network interfaces for the "cpu" and
65 NB: for the past 15 years, the DSA subsystem had been making use of the terms
[all …]
H A Dbcm_sf2.rst41 The driver is located in ``drivers/net/dsa/bcm_sf2.c`` and is implemented as a DSA
51 Overall, the SF2 driver is a fairly regular DSA driver; there are a few
57 The DSA platform device driver is probed using a specific compatible string
58 provided in ``net/dsa/dsa.c``. The reason for that is because the DSA subsystem gets
59 registered as a platform device driver currently. DSA will provide the needed
70 Broadcom switches connected to a SF2 require the use of the DSA user MDIO bus
74 "double" programming. Using DSA, and setting ``ds->phys_mii_mask`` accordingly, we
H A Dlan9303.rst13 The driver is implemented as a DSA driver, see ``Documentation/networking/dsa/dsa.rst``.
21 interfaces (which is the default state of a DSA device). Due to HW limitations,
H A Db53.rst17 DSA driver; see ``Documentation/networking/dsa/dsa.rst`` for details on the
36 DSA driver and will work like all DSA drivers which supports tagging.
/linux/certs/
H A DKconfig43 bool "ML-DSA-44"
47 Use an ML-DSA-44 key (NIST FIPS 204) for module signing. ML-DSA
51 ML-DSA.
54 bool "ML-DSA-65"
58 Use an ML-DSA-65 key (NIST FIPS 204) for module signing. ML-DSA
62 ML-DSA.
65 bool "ML-DSA-87"
69 Use an ML-DSA-87 key (NIST FIPS 204) for module signing. ML-DSA
73 ML-DSA.
191 def_bool $(success, openssl list -key-managers | grep -q ML-DSA-87)
[all …]
/linux/Documentation/ABI/testing/
H A Dsysfs-class-net-dsa7 tagging protocol used by the DSA network devices that are
10 attached DSA switches, if this operation is supported by the
11 driver. Changing the tagging protocol must be done with the DSA
H A Dsysfs-bus-event_source-devices-dsa7 perf_event_attr.config1 for the IDXD DSA pmu. (See also
13 IDXD DSA Spec for possible attribute values)::
29 IDXD DSA pmu is bound for access to all dsa pmu
/linux/crypto/asymmetric_keys/
H A DKconfig58 bool "Waive rejection of authenticatedAttributes for ML-DSA"
62 Due to use of CMS_NOATTR with ML-DSA not being supported in
64 allows authenticatedAttributes to be used with ML-DSA for
/linux/drivers/net/dsa/sja1105/
H A DKconfig32 the SJA1105 DSA driver.
41 engine in the SJA1105 DSA driver, which is controlled using a
/linux/Documentation/ABI/stable/
H A Dsysfs-driver-dma-idxd50 The read buffers represent resources within the DSA
52 support operations. See DSA spec v1.2 9.2.4 Total Read Buffers.
127 device. See DSA spec v1.2 9.2.8 GENCFG on Global Read Buffer Limit.
150 DSA cap value is a 64 bit hex value.
151 This attribute should only be visible on DSA devices of version
304 Description: Enable the use of global read buffer limit for the group. See DSA
314 by all engines in the group. See DSA spec v1.2 9.2.18 GRPCFG Read
324 engines in the group. See DSA spec v1.2 9.2.18 GRPCFG Read Buffers
/linux/Documentation/networking/
H A Dtimestamping.rst684 3.2.1 DSA (Distributed Switch Architecture) switches
689 a port multiplier with optional forwarding acceleration features. Each DSA
694 When a DSA switch is attached to a host port, PTP synchronization has to
696 jitter between the host port and its PTP partner. For this reason, some DSA
699 measure wire and PHY propagation latencies. Timestamping DSA switches are
701 for the fact that the DSA interfaces are in fact virtual in terms of network
703 interfaces of a DSA switch to share the same PHC.
705 By design, PTP timestamping with a DSA switch does not need any special
707 host port also supports PTP timestamping, DSA will take care of intercepting
711 anybody else except for the DSA switch port must be prevented from doing so.
[all …]
/linux/net/dsa/
H A DKconfig88 tristate "Tag driver for Marvell switches using DSA headers"
92 Marvell switches which use DSA headers.
95 tristate "Tag driver for Marvell switches using EtherType DSA headers"
99 Marvell switches which use EtherType DSA headers.
/linux/Documentation/devicetree/bindings/net/
H A Dhisilicon-hns-dsaf.txt1 Hisilicon DSA Fabric device controller
12 - interrupts: should contain the DSA Fabric and rcb interrupt.
/linux/lib/crypto/tests/
H A DKconfig39 tristate "KUnit tests for ML-DSA" if !KUNIT_ALL_TESTS
44 KUnit tests for the ML-DSA digital signature algorithm.
/linux/drivers/net/ethernet/mscc/
H A DKconfig24 used by switchdev as well as by DSA drivers.
/linux/drivers/net/dsa/
H A DKconfig20 tristate "DSA mock-up Ethernet switch chip support"
25 exercises the DSA APIs.
/linux/Documentation/admin-guide/
H A Dmodule-signing.rst32 and NIST FIPS-204 ML-DSA public key signing standards (though it is pluggable
35 algorithm is selected by data in the signature); ML-DSA does its own hashing,
152 (``MODULE_SIG_KEY_TYPE_ECDSA``) and ML-DSA (``MODULE_SIG_KEY_TYPE_MLDSA_*``) to
153 generate an RSA 4k, a NIST P-384 keypair or an ML-DSA 44, 65 or 87 keypair.
/linux/Documentation/devicetree/bindings/net/dsa/
H A Dlan9303.txt21 Note: always use 'reg = <0/1/2>;' for the three DSA ports, even if the device is
/linux/arch/arm/boot/dts/aspeed/
H A Daspeed-bmc-facebook-elbert.dts192 * BCM53134 is added to "bcm53xx" DSA driver.
/linux/arch/arm/boot/dts/intel/ixp/
H A Dintel-ixp42x-ixdpg425.dts93 * of Realtek DSA switch on the board.
/linux/arch/arm/boot/dts/marvell/
H A Dkirkwood-linksys-viper.dts226 /* eth1 is connected to the switch at port 6. However DSA only supports a
H A Dorion5x-netgear-wnr854t.dts212 /* Hardwired to DSA switch */
/linux/arch/arm64/boot/dts/marvell/
H A Darmada-3720-espressobin.dtsi16 /* for DSA user port device */

12