| /linux/net/ipv4/ |
| H A D | tcp_recovery.c | 16 if (tp->sacked_out >= tp->reordering && in tcp_rack_reo_wnd() 147 if ((state < TCP_CA_Recovery && tp->sacked_out >= tp->reordering) || in tcp_newreno_mark_lost()
|
| H A D | tcp_metrics.c | 450 if (val < tp->reordering && in tcp_update_metrics() 451 tp->reordering != in tcp_update_metrics() 454 tp->reordering); in tcp_update_metrics() 498 if (val && tp->reordering != val) in tcp_init_metrics() 499 tp->reordering = val; in tcp_init_metrics()
|
| H A D | tcp_input.c | 623 nr_segs = max_t(u32, nr_segs, tp->reordering + 1); in tcp_sndbuf_expand() 1288 if ((metric > tp->reordering * mss) && mss) { in tcp_check_sack_reordering() 1292 tp->reordering, in tcp_check_sack_reordering() 1297 tp->reordering = min_t(u32, (metric + mss - 1) / mss, in tcp_check_sack_reordering() 2443 tp->reordering = min_t(u32, tp->packets_out + addend, in tcp_check_reno_reordering() 2559 u8 reordering; in tcp_enter_loss() local 2580 reordering = READ_ONCE(net->ipv4.sysctl_tcp_reordering); in tcp_enter_loss() 2582 tp->sacked_out >= reordering) in tcp_enter_loss() 2583 tp->reordering = min_t(unsigned int, tp->reordering, in tcp_enter_loss() 2584 reordering); in tcp_enter_loss() [all …]
|
| /linux/Documentation/dev-tools/ |
| H A D | kcsan.rst | 225 memory operation from reordering before the barrier. Developers should 285 based on modeling access reordering (with ``CONFIG_KCSAN_WEAK_MEMORY=y``). 287 simulated reordering within the scope of its function (at most 1 in-flight 290 Once an access has been selected for reordering, it is checked along every 293 reordering. 312 simulated reordering. After the write of ``flag``, ``x`` is again checked for 315 would not be considered for reordering after the proper release of ``flag``, 323 accesses, and the only access type for which KCSAN simulates reordering. This 324 means reordering of marked accesses is not modeled.
|
| /linux/tools/memory-model/litmus-tests/ |
| H A D | LB+unlocklockonceonce+poacquireonce.litmus | 10 * the viewpoint of another CPU (the kind of reordering allowed by TSO).
|
| /linux/tools/testing/selftests/net/packetdrill/ |
| H A D | tcp_limited_transmit_limited-transmit-sack.pkt | 32 // It turned out to be reordering, not loss.
|
| H A D | tcp_limited_transmit_limited-transmit-no-sack.pkt | 32 // It turned out to be reordering, not loss.
|
| H A D | tcp_sack_sack-shift-sacked-7-3-4-8-9-fack.pkt | 24 // RACK reordering timer
|
| /linux/drivers/platform/x86/amd/ |
| H A D | Kconfig | 16 that alters CPU core reordering. This bias prefers cores with higher
|
| /linux/Documentation/devicetree/bindings/mtd/ |
| H A D | gpio-control-nand.txt | 23 location used to guard against bus reordering with regards to accesses to
|
| /linux/tools/testing/selftests/bpf/progs/ |
| H A D | bpf_cc_cubic.c | 98 if (tcp_sk(sk)->reordering > TCP_REORDERING) in tcp_may_raise_cwnd()
|
| /linux/Documentation/block/ |
| H A D | blk-mq.rst | 98 any reordering. When the device starts processing requests in the hardware 119 There is no reordering at this stage, and each software queue has a set of
|
| /linux/include/linux/ |
| H A D | tcp.h | 210 u32 reordering; /* Packet reordering metric. */ member
|
| /linux/Documentation/networking/net_cachelines/ |
| H A D | tcp_sock.rst | 89 u32 reordering read_mostly tcp_s…
|
| /linux/Documentation/arch/x86/ |
| H A D | amd-hfi.rst | 83 a reordering of the performance and efficiency ranking. Table updates happen
|
| /linux/tools/perf/Documentation/ |
| H A D | perf.data-file-format.txt | 490 below). perf record guarantees that there is no reordering over a 549 No event reordering over this header. No payload.
|
| /linux/Documentation/networking/ |
| H A D | xsk-tx-metadata.rst | 81 packet reordering, a packet with a launch time request will block other
|
| H A D | nexthop-group-resilient.rst | 42 the same server, the issue is that different latencies and reordering along
|
| /linux/Documentation/core-api/ |
| H A D | padata.rst | 13 decryption on large numbers of packets without reordering those packets. This
|
| /linux/Documentation/admin-guide/blockdev/ |
| H A D | zoned_loop.rst | 101 ordered_zone_append Enable zloop mitigation of zone append reordering.
|
| /linux/Documentation/ |
| H A D | memory-barriers.txt | 367 can use a variety of tricks to improve performance, including reordering, 919 (*) Control dependencies require that the compiler avoid reordering the 1547 (*) Prevents the compiler from reordering accesses following the 1875 compiler and the CPU from reordering them. 2059 respectively, this same reordering can occur if the lock's ACQUIRE and 2078 It might appear that this reordering could introduce a deadlock. 2085 the reordering, not the compiler. If the compiler (or, for 2352 Under normal operation, memory operation reordering is generally not going to 2355 circumstances in which reordering definitely _could_ be a problem: 2879 and st.rel instructions (respectively) that prevent such reordering.
|
| /linux/Documentation/admin-guide/media/ |
| H A D | imx.rst | 54 along with block reordering, in coordination with vertical flip. 208 pixel reordering within the same colorspace can be carried out by the 324 de-interlace without motion compensation, and pixel reordering.
|
| /linux/Documentation/filesystems/ |
| H A D | romfs.rst | 179 from the filesystem. It might be resolved by reordering file data to
|
| /linux/Documentation/networking/device_drivers/ethernet/freescale/ |
| H A D | dpaa.rst | 199 This ensures a very low rate of frame reordering. A drawback of this
|
| /linux/tools/memory-model/Documentation/ |
| H A D | control-dependencies.txt | 242 (*) Control dependencies require that the compiler avoid reordering the
|