From: John Fastabend <john.fastabend@gmail.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
netdev@vger.kernel.org
Subject: Re: TX vs RX pause frame question
Date: Sun, 26 Mar 2017 10:55:30 -0700 [thread overview]
Message-ID: <58D80092.9020902@gmail.com> (raw)
In-Reply-To: <1490523071.3177.56.camel@kernel.crashing.org>
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
next prev parent reply other threads:[~2017-03-26 18:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-26 10:11 TX vs RX pause frame question Benjamin Herrenschmidt
2017-03-26 17:55 ` John Fastabend [this message]
2017-03-26 21:08 ` Benjamin Herrenschmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=58D80092.9020902@gmail.com \
--to=john.fastabend@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).