• Ursula Braun's avatar
    net/smc: optimize consumer cursor updates · 99be51f1
    Ursula Braun authored
    The SMC protocol requires to send a separate consumer cursor update,
    if it cannot be piggybacked to updates of the producer cursor.
    Currently the decision to send a separate consumer cursor update
    just considers the amount of data already received by the socket
    program. It does not consider the amount of data already arrived, but
    not yet consumed by the receiver. Basing the decision on the
    difference between already confirmed and already arrived data
    (instead of difference between already confirmed and already consumed
    data), may lead to a somewhat earlier consumer cursor update send in
    fast unidirectional traffic scenarios, and thus to better throughput.
    Signed-off-by: default avatarUrsula Braun <ubraun@linux.ibm.com>
    Suggested-by: default avatarThomas Richter <tmricht@linux.ibm.com>
    Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
    99be51f1
smc_tx.c 16.1 KB