From: Andrew Lunn <andrew@lunn.ch>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: madalin.bucur@oss.nxp.com,
"David S. Miller" <davem@davemloft.net>,
Florian Fainelli <f.fainelli@gmail.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
netdev <netdev@vger.kernel.org>,
ykaukab@suse.de
Subject: Re: [PATCH v2 2/2] dpaa_eth: support all modes with rate adapting PHYs
Date: Mon, 27 Jan 2020 17:04:13 +0100 [thread overview]
Message-ID: <20200127160413.GI13647@lunn.ch> (raw)
In-Reply-To: <CA+h21hqzR72v9=dWGk1zBptNHNst+kajh6SHHSUMp02fAq5m5g@mail.gmail.com>
> Is this sufficient?
> I suppose this works because you have flow control enabled by default?
> What would happen if the user would disable flow control with ethtool?
It will still work. Network protocols expect packets to be dropped,
there are bottlenecks on the network, and those bottlenecks change
dynamically. TCP will still be able to determine how much traffic it
can send without too much packet loss, independent of if the
bottleneck is here between the MAC and the PHY, or later when it hits
an RFC 1149 link.
Andrew
next prev parent reply other threads:[~2020-01-27 16:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 15:07 [PATCH v2 0/2] net: phy: aquantia: indicate rate adaptation Madalin Bucur
2020-01-27 15:07 ` [PATCH v2 1/2] net: phy: aquantia: add rate_adaptation indication Madalin Bucur
2020-01-27 15:07 ` [PATCH v2 2/2] dpaa_eth: support all modes with rate adapting PHYs Madalin Bucur
2020-01-27 15:31 ` Vladimir Oltean
2020-01-27 15:49 ` Madalin Bucur (OSS)
2020-01-27 16:04 ` Andrew Lunn [this message]
2020-01-28 15:41 ` Vladimir Oltean
2020-01-28 16:23 ` Andrew Lunn
2020-01-29 9:09 ` Madalin Bucur (OSS)
2020-01-29 10:19 ` Vladimir Oltean
2020-01-29 10:58 ` Madalin Bucur (OSS)
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=20200127160413.GI13647@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=madalin.bucur@oss.nxp.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=ykaukab@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.