| /f-stack/dpdk/lib/librte_acl/ |
| H A D | acl_vect.h | 25 #define ACL_TR_HILO(P, TC, tr0, tr1, lo, hi) do { \ argument 26 lo = (typeof(lo))_##P##_shuffle_ps((TC)(tr0), (TC)(tr1), 0x88); \ 27 hi = (typeof(hi))_##P##_shuffle_ps((TC)(tr0), (TC)(tr1), 0xdd); \
|
| /f-stack/freebsd/contrib/device-tree/Bindings/mfd/ |
| H A D | atmel-tcb.txt | 7 - interrupts: Should contain all interrupts for the TC block 8 Note that you can specify several interrupt cells if the TC 24 One interrupt per TC block: 45 One interrupt per TC channel in a TC block:
|
| /f-stack/dpdk/app/test/ |
| H A D | test_sched.c | 22 #define TC 2 macro 114 ip_hdr->dst_addr = RTE_IPV4(0,0,TC,QUEUE); in prepare_pkt() 117 rte_sched_port_pkt_write(port, mbuf, SUBPORT, PIPE, TC, QUEUE, in prepare_pkt() 183 TEST_ASSERT_EQUAL(traffic_class, TC, "Wrong traffic_class\n"); in test_sched() 193 TEST_ASSERT_EQUAL(subport_stats.n_pkts_tc[TC-1], 10, "Wrong subport stats\n"); in test_sched()
|
| /f-stack/freebsd/contrib/device-tree/Bindings/soc/microchip/ |
| H A D | atmel,at91rm9200-tcb.yaml | 32 interrupt for the TC block 121 /* One interrupt per TC block: */ 142 /* One interrupt per TC channel in a TC block: */
|
| /f-stack/dpdk/doc/guides/prog_guide/ |
| H A D | qos_framework.rst | 187 …| | | Lowest priority TC: 4 | exactly 1 queue, while the lowest prio… 536 * Traffic class TC is the highest priority active traffic class of pipe P; 538 * Queue Q is the next queue selected by WRR within traffic class TC of pipe P; 542 * Subport S has enough credits for traffic class TC to send the packet; 546 * Pipe P has enough credits for traffic class TC to send the packet. 550 subport S traffic class TC, pipe P, pipe P traffic class TC. 738 Therefore, queue 0 (associated with TC 0, highest priority TC) is handled before 739 queue 1 (TC 1, lower priority than TC 0), 740 which is handled before queue 2 (TC 2, lower priority than TC 1) and it conitnues until queues of a… 741 lowest priority TC are handled. At last, queues 12..15 (best effort TC, lowest priority TC) are han… [all …]
|
| H A D | glossary.rst | 216 TC
|
| H A D | rte_flow.rst | 1053 - ``label_tc_s_ttl``: label, TC, Bottom of Stack and TTL.
|
| /f-stack/dpdk/devtools/ |
| H A D | check-abi-version.sh | 31 OBJ_DUMP_OUTPUT=`objdump -TC --section=.text ${LIB} 2>&1 | grep ".text"`
|
| H A D | words-case.txt | 58 TC
|
| /f-stack/freebsd/contrib/device-tree/Bindings/dma/ |
| H A D | ti-edma.txt | 4 Controller(s) (TC). The CC is the main entry for DMA users since it is 19 number and the second is the TC the channel is serviced on. 61 - reg: Memory map of eDMA TC 67 - ti,hwmods: Name of the hwmods associated to the eDMA TC.
|
| H A D | ti-dma-crossbar.txt | 27 dmas = <&edma_xbar 12 0 1>; where <12> is the DMA request number, <0> is the TC
|
| /f-stack/freebsd/contrib/device-tree/src/arm/ |
| H A D | sama5d3_tcb1.dtsi | 4 * 2 TC blocks.
|
| /f-stack/freebsd/contrib/device-tree/Bindings/ufs/ |
| H A D | tc-dwc-g210-pltfrm.txt | 19 Example for a setup using a 1.40a DWC Controller with a 6.00 G210 40-bit TC:
|
| /f-stack/freebsd/contrib/device-tree/Bindings/sound/ |
| H A D | davinci-mcbsp.txt | 20 TC channel ordered triplets.
|
| /f-stack/dpdk/doc/guides/howto/ |
| H A D | vfd.rst | 346 VF TC bandwidth allocation 359 VF TC max bandwidth 370 TC strict priority scheduling 378 The 0 in the TC bitmap means disabling the strict priority scheduling for this 379 TC. To enable use a value of 1.
|
| /f-stack/dpdk/doc/guides/nics/ |
| H A D | i40e.rst | 658 VF & TC max bandwidth setting 661 The per VF max bandwidth and per TC max bandwidth cannot be enabled in parallel. 662 The behavior is different when handling per VF and per TC max bandwidth setting. 663 When enabling per VF max bandwidth, SW will check if per TC max bandwidth is 665 When enabling per TC max bandwidth, SW will check if per VF max bandwidth 666 is enabled. If so, disable per VF max bandwidth and continue with per TC max 669 TC TX scheduling mode setting 673 If a TC is set to strict priority mode, it can consume unlimited bandwidth. 674 It means if APP has set the max bandwidth for that TC, it comes to no 676 It's suggested to set the strict priority mode for a TC that is latency
|
| H A D | mvpp2.rst | 248 - ``<pcp_list>``: List of PCP values to handle in particular TC (e.g. 0 1 3-4 7). 250 - ``<dscp_list>``: List of DSCP values to handle in particular TC (e.g. 0-12 32-48 63). 278 Setting PCP/DSCP values for the default TC is not required. All PCP/DSCP 279 values not assigned explicitly to particular TC will be handled by the 280 default TC.
|
| H A D | tap.rst | 52 just after netdevice creation. Using TC rules, traffic from the remote netdevice 128 As rules are translated to TC, it is possible to show them with something like::
|
| /f-stack/dpdk/doc/guides/sample_app_ug/ |
| H A D | vmdq_dcb_forwarding.rst | 35 …./<build_dir>/examples/dpdk-vmdq_dcb [EAL options] -- -p PORTMASK --nb-pools NP --nb-tcs TC --enab… 37 where, NP can be 16 or 32, TC can be 4 or 8, rss is disabled by default.
|
| H A D | qos_scheduler.rst | 375 …| Queue | High Priority TC: 1, | Queue of lowest priority traffic | De… 376 …| | Lowest Priority TC: 4 | class (Best effort) serviced in WRR | …
|
| /f-stack/dpdk/doc/guides/rel_notes/ |
| H A D | release_17_05.rst | 123 * **Added VF TC min and max bandwidth setting in i40e.** 125 Enabled capability to set the min and max allocated bandwidth for a TC on a 128 * **Added TC strict priority mode setting on i40e.** 132 is now possible to change the Tx scheduling mode for a TC. This is a global
|
| H A D | release_20_11.rst | 571 a TC is greater than 256.
|
| /f-stack/freebsd/sys/ |
| H A D | pmc.h | 249 __PMC_MODE(TC, 3)
|
| /f-stack/dpdk/drivers/net/iavf/ |
| H A D | iavf_fdir.c | 622 VIRTCHNL_ADD_PROTO_HDR_FIELD_BIT(hdr, IPV6, TC); in iavf_fdir_parse_pattern()
|
| /f-stack/dpdk/doc/guides/testpmd_app_ug/ |
| H A D | testpmd_funcs.rst | 178 * ``dcb_tc``: DCB information such as TC mapping. 1483 Set a TC's TX max absolute bandwidth (Mbps) for a VF from PF::
|