| /linux/Documentation/translations/zh_CN/infiniband/ |
| H A D | opa_vnic.rst | 78 0-7 L4 type (=0x78 ETHERNET)
87 16-31 L4 头
|
| /linux/drivers/cpufreq/ |
| H A D | s5pv210-cpufreq.c | 110 L0, L1, L2, L3, L4, enumerator
129 {0, L4, 100*1000},
161 [L4] = {
187 /* L4 : [100/100/100][83/83][66/66][100/100] */
268 if ((index == L4) || (priv_index == L4)) in s5pv210_target()
322 * 3. DMC1 refresh count for 133Mhz if (index == L4) is in s5pv210_target()
434 * L4 : DMC1 = 100Mhz 7.8us/(1/100) = 0x30c in s5pv210_target()
442 * L4 level needs to change memory bus speed, hence ONEDRAM clock in s5pv210_target()
456 if (index != L4) { in s5pv210_target()
[all...] |
| /linux/arch/riscv/lib/ |
| H A D | tishift.S | 37 blez a5, .L4
46 .L4: label
|
| /linux/lib/ |
| H A D | test_dynamic_debug.c | 92 enum cat_level_names { L0 = 22, L1, L2, L3, L4, L5, L6, L7 }; enumerator
94 "L0", "L1", "L2", "L3", "L4", "L5", "L6", "L7");
136 prdbg(L4); in do_levels()
|
| /linux/Documentation/devicetree/bindings/arm/omap/ |
| H A D | l4.txt | 1 L4 interconnect bindings
3 These bindings describe the OMAP SoCs L4 interconnect bus.
|
| /linux/arch/arm/boot/dts/gemini/ |
| H A D | gemini-wbd111.dts | 51 label = "wbd111:green:L4";
57 label = "wbd111:red:L4";
|
| H A D | gemini-wbd222.dts | 50 label = "wbd111:green:L4";
56 label = "wbd111:red:L4";
|
| /linux/arch/m68k/lib/ |
| H A D | udivsi3.S | 108 L4: lsrl IMM (1), d1 /* shift divisor */ label
111 jcc L4
|
| /linux/arch/sparc/net/ |
| H A D | bpf_jit_64.h | 24 #define L4 0x14 macro
|
| /linux/arch/xtensa/lib/ |
| H A D | memset.S | 88 bbci.l a4, 1, .L4
92 .L4: label
|
| H A D | memcopy.S | 162 bbsi.l a4, 1, .L4
171 bbsi.l a4, 1, .L4
174 .L4: label
|
| H A D | usercopy.S | 182 bbci.l a4, 1, .L4
188 .L4: label
|
| /linux/Documentation/infiniband/ |
| H A D | opa_vnic.rst | 69 0-7 L4 type (=0x78 ETHERNET)
78 16-31 L4 header
97 The L4 header field contains the virtual Ethernet switch id the VNIC port
|
| /linux/Documentation/networking/device_drivers/ethernet/microsoft/ |
| H A D | netvsc.rst | 29 For TCP & UDP, we can switch hash level between L3 and L4 by ethtool
31 hash level is L4. We currently only allow switching TX hash level
34 On Azure, fragmented UDP packets have high loss rate with L4
|
| /linux/Documentation/bpf/ |
| H A D | prog_sk_lookup.rst | 84 * L4 protocol identifier (``IPPROTO_TCP`` or ``IPPROTO_UDP``),
86 * source and destination L4 port,
|
| /linux/drivers/net/ethernet/intel/libie/ |
| H A D | rx.c | 49 LIBIE_RX_PT(IPV##oip, NOT_FRAG, tun, teprot, NOT_FRAG, iprot, L4)
|
| /linux/Documentation/networking/device_drivers/ethernet/freescale/dpaa2/ |
| H A D | ethernet-driver.rst | 182 traffic based on a 5-tuple key: src IP, dst IP, IP proto, L4 src port,
183 L4 dst port. No user configuration is supported for now.
|
| /linux/arch/arm/boot/dts/ti/omap/ |
| H A D | omap4460.dtsi | 86 /* Only some L4 CFG interconnect ranges are different on 4460 */
|
| H A D | omap5-l4-abe.dtsi | 17 /* CPU to L4 ABE mapping */
53 /* L3 to L4 ABE mapping */
|
| H A D | omap4-l4-abe.dtsi | 17 /* CPU to L4 ABE mapping */
53 /* L3 to L4 ABE mapping */
|
| /linux/Documentation/networking/device_drivers/ethernet/aquantia/ |
| H A D | atlantic.rst | 263 3. 8 L3/L4 5-Tuple rules
281 - Locations 32 - 39 for L3/L4 5-tuple filters (locations 32, 36 for IPv6)
283 The L3/L4 5-tuple (protocol, source and destination IP address, source and
360 RX Flow L3/L4 rule may be used.
|
| /linux/Documentation/networking/devlink/ |
| H A D | devlink-eswitch-attr.rst | 51 * ``transport`` L4 mode.
|
| /linux/Documentation/locking/ |
| H A D | rt-mutex-design.rst | 139 Mutexes: L1, L2, L3, L4
147 D owns L4
148 E blocked on L4
152 E->L4->D->L3->C->L2->B->L1->A
166 E->L4->D->L3->C->L2-+
185 E->L4->D->L3->C-+
|
| /linux/arch/arm64/boot/dts/qcom/ |
| H A D | sm8250-xiaomi-pipa.dts | 231 /* L4 - lmx.lvl (ARC) */
443 /* L3 & L4 are unused. */
|
| /linux/Documentation/networking/ |
| H A D | iou-zcrx.rst | 26 Required to split packets at the L4 boundary into a header and a payload.
|