netdev - Re: TX vs RX pause frame question

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <58D80092.9020902@gmail.com>
Date:   Sun, 26 Mar 2017 10:55:30 -0700
From:   John Fastabend <john.fastabend@...il.com>
To:     Benjamin Herrenschmidt <benh@...nel.crashing.org>,
        netdev@...r.kernel.org
Subject: Re: TX vs RX pause frame question

On 17-03-26 03:11 AM, Benjamin Herrenschmidt wrote:
> Hi !
> 
> It's not 100% clear to me looking at various drivers what is
> considered "rx_pause" and what is "tx_pause" (from the ethtool
> terminology).
> 
> Is "rx_pause" about receiving pause frame to throttle the transmitter
> or is it about sending pause frames when the receiver gets full ?
> 
> Thanks,
> Ben.
> 

The common implementation, at least on the Intel devices, is rx_pause
should be enabled so the device will respond to receiving a pause frame, e.g.
stop sending packets. And tx_pause is for enabling/disabling sending of
pause frames.

Thanks,
John