Searched full:classified (Results 1 – 25 of 99) sorted by relevance
1234
| /Linux-v6.6/drivers/net/ethernet/microchip/vcap/ |
| D | vcap_ag_api.h | 60 * Keys ending in _CLS are classified frame data
84 * Classified DEI
92 * Classified PCP
109 * Classified VID
184 * Classified ISDX
186 * Set if classified ISDX > 0
287 * is taken from classified results (VID, DSCP) and frame (SPORT, DPORT, ETYPE,
316 * Classified Policy Association Group: chains rules from IS1/CLM to IS2
340 * Classified RTP_ID
510 * Controls the classified VID: 0: VID_NONE: No action. 1: VID_ADD: New VID =
[all …]
|
| /Linux-v6.6/drivers/net/ethernet/microchip/lan966x/ |
| D | lan966x_ifh.h | 54 /* Classified DSCP value of frame */
75 /* Stagd flag and classified TCI of frame (PCP/DEI/VID) */
78 /* Classified internal priority for queuing */
98 /* ISDX as classified by S1 */
110 /* Classified internal priority for resourcemgt, tagging etc */
|
| D | lan966x_port.c | 475 /* Map the values only if it is enabled otherwise will be the classified in lan966x_port_qos_pcp_rewr_set()
518 /* Map each classified Qos class and DP to classified DSCP value */ in lan966x_port_qos_dscp_rewr_set()
|
| /Linux-v6.6/drivers/net/ethernet/microchip/sparx5/ |
| D | sparx5_dcb.c | 188 * not indicate DP level, so we map classified QoS class to in sparx5_dcb_app_update()
189 * classified DSCP, for each classified DP level. Rewrite of in sparx5_dcb_app_update()
217 * classified DSCP will then be zero for all classified in sparx5_dcb_app_update()
399 /* Enable DSCP classification based on classified QoS class and in sparx5_dcb_init()
|
| D | sparx5_port.c | 1173 /* Use mapping table, with classified QoS as index, to map QoS and DP in sparx5_port_qos_pcp_rewr_set()
1174 * to tagged PCP and DEI, if PCP is trusted. Otherwise use classified in sparx5_port_qos_pcp_rewr_set()
1175 * PCP. Classified PCP equals frame PCP. in sparx5_port_qos_pcp_rewr_set()
1193 /* Rewrite PCP and DEI, for each classified QoS class and DP in sparx5_port_qos_pcp_rewr_set()
1266 /* On egress, rewrite DSCP value to either classified DSCP or frame in sparx5_port_qos_dscp_rewr_set()
1267 * DSCP. If enabled; classified DSCP, if disabled; frame DSCP. in sparx5_port_qos_dscp_rewr_set()
1276 /* On ingress, map each classified QoS class and DP to classified DSCP in sparx5_port_qos_dscp_rewr_set()
|
| /Linux-v6.6/net/dsa/ |
| D | tag_ocelot.c | 13 * the packet to the bridge VLAN. Otherwise, leave the classified VLAN at zero,
162 * 802.1Q header does not (the classified VLAN only becomes visible on in ocelot_rcv()
165 * classified VLAN and manually replace the existing 802.1Q header from in ocelot_rcv()
169 * frame to remain unmodified, because the classified VLAN is always in ocelot_rcv()
|
| /Linux-v6.6/include/linux/ |
| D | netfilter_netdev.h | 65 * @skb: packet to be classified
72 * On ingress, packets are classified first by tc, then by netfilter.
|
| /Linux-v6.6/Documentation/devicetree/bindings/bus/ |
| D | ti,da850-mstpri.txt | 5 peripherals classified as masters.
|
| /Linux-v6.6/Documentation/ABI/testing/ |
| D | sysfs-firmware-opal-sensor-groups | 7 which are classified based on type of the sensor
|
| /Linux-v6.6/Documentation/virt/ |
| D | paravirt_ops.rst | 21 pv_ops operations are classified into three categories:
|
| /Linux-v6.6/Documentation/devicetree/bindings/arm/ |
| D | arm,coresight-etb10.yaml | 18 SoCs tracing needs. These trace components can generally be classified as
|
| D | arm,coresight-tpiu.yaml | 18 SoCs tracing needs. These trace components can generally be classified as
|
| D | arm,coresight-dummy-source.yaml | 12 SoCs tracing needs. These trace components can generally be classified as
|
| D | arm,coresight-dummy-sink.yaml | 12 SoCs tracing needs. These trace components can generally be classified as
|
| D | arm,coresight-static-funnel.yaml | 18 SoCs tracing needs. These trace components can generally be classified as
|
| D | arm,coresight-stm.yaml | 18 SoCs tracing needs. These trace components can generally be classified as
|
| D | arm,coresight-static-replicator.yaml | 18 SoCs tracing needs. These trace components can generally be classified as
|
| D | arm,coresight-catu.yaml | 18 SoCs tracing needs. These trace components can generally be classified as
|
| D | arm,coresight-dynamic-funnel.yaml | 18 SoCs tracing needs. These trace components can generally be classified as
|
| D | arm,coresight-dynamic-replicator.yaml | 18 SoCs tracing needs. These trace components can generally be classified as
|
| D | arm,coresight-tmc.yaml | 18 SoCs tracing needs. These trace components can generally be classified as
|
| /Linux-v6.6/net/sched/ |
| D | sch_hhf.c | 19 * Flows are classified into two buckets: non-heavy-hitter and heavy-hitter
20 * buckets. Initially, a new flow starts as non-heavy-hitter. Once classified
44 * susceptible to false positives (non-heavy-hitters mistakenly classified as
59 * Once a flow is classified as heavy-hitter, we also save its per-flow state
|
| /Linux-v6.6/Documentation/networking/devlink/ |
| D | netdevsim.rst | 97 - When a packet enters the device it is classified to a filtering
|
| /Linux-v6.6/Documentation/PCI/ |
| D | pcieaer-howto.rst | 102 PCIe errors are classified into two types: correctable errors
116 errors are further classified into non-fatal errors and fatal errors.
|
| /Linux-v6.6/Documentation/ABI/stable/ |
| D | sysfs-firmware-efi-vars | 10 In summary, EFI variables are named, and are classified
|
1234
