From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Jason Cooper <jason@lakedaemon.net>
Cc: Gregory CLEMENT <gregory.clement@free-electrons.com>,
Simon Guinot <simon.guinot@sequanux.org>,
Andrew Lunn <andrew@lunn.ch>,
netdev@vger.kernel.org, Vincent Donnefort <vdonnefort@gmail.com>,
stable@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH v2 1/3] net: mvneta: introduce compatible string "marvell, armada-xp-neta"
Date: Thu, 18 Jun 2015 09:31:51 +0200 [thread overview]
Message-ID: <20150618093151.6efcd32a@free-electrons.com> (raw)
In-Reply-To: <20150617213926.GE2917@io.lakedaemon.net>
Dear Jason Cooper,
On Wed, 17 Jun 2015 21:39:26 +0000, Jason Cooper wrote:
> Odd, I'd use that as an example of the process working. ;-) we have
> everyone using 'armada-370-neta' for a given block. We discovered that
> the original IP block (on the 370s) had a limitation (no hw checksum
> for greater than 1600 bytes). A newer version of the IP block (XP)
> doesn't have the limitation.
>
> So we change the driver to honor the limit for the 370 compatible
> string. We create a new compatible string for xp where the block
> doesn't have the limitation.
>
> How did the process fail?
Because now all Armada XP users of jumbo frames are looking the HW
checksum on their jumbo frames, which you can consider to be a
regression: it was working, it is no longer working.
Of course, since it falls back to SW checksumming, it still "works",
but some users can complain of the performance penalty and consider it
to be a regression.
If on Armada XP, we had used for the beginning:
compatible = "marvell,armada-xp-neta", "marvell,armada-370-neta"
with only marvell,armada-370-neta supported originally, we could have
added this fix without breaking HW checksumming on jumbo frames for
Armada XP users.
So I'm sorry, but the process indeed failed, because Armada XP users
keeping their old Device Tree blob will see a regression.
> I'm not seeing where backwards compatibility was broken? A device with
> an old dtb booting a newer kernel gets a bugfix. In the case of an XP
> board with an old dtb (armada-370-neta), the hardware still works, but
> not optimally. Upgrading the dtb will enable hw checksumming for jumbo
> packets.
"not optimally" is still a breakage.
Again, I personally don't care about DT backward compatibility as I
think it's a stupid requirement. But I like to point out to the
DT backward compatibility fanatics when it was actually broken :-)
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-06-18 7:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1434547162-6275-1-git-send-email-simon.guinot@sequanux.org>
2015-06-17 13:19 ` [PATCH v2 1/3] net: mvneta: introduce compatible string "marvell,armada-xp-neta" Simon Guinot
2015-06-17 15:12 ` Gregory CLEMENT
2015-06-17 15:15 ` [PATCH v2 1/3] net: mvneta: introduce compatible string "marvell, armada-xp-neta" Gregory CLEMENT
2015-06-17 17:01 ` Jason Cooper
2015-06-17 20:43 ` Thomas Petazzoni
2015-06-17 21:39 ` Jason Cooper
2015-06-18 7:31 ` Thomas Petazzoni [this message]
2015-06-19 12:32 ` Simon Guinot
2015-06-25 9:13 ` Simon Guinot
2015-06-25 13:20 ` Jason Cooper
2015-06-29 13:03 ` Gregory CLEMENT
2015-06-29 13:03 ` [PATCH v2 1/3] net: mvneta: introduce compatible string "marvell,armada-xp-neta" Gregory CLEMENT
2015-06-17 13:19 ` [PATCH v2 2/3] ARM: mvebu: update Ethernet compatible string for Armada XP Simon Guinot
2015-06-29 13:04 ` Gregory CLEMENT
2015-06-17 13:19 ` [PATCH v2 3/3] ARM: mvebu: disable IP checksum with jumbo frames for Armada 370 Simon Guinot
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=20150618093151.6efcd32a@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=andrew@lunn.ch \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=simon.guinot@sequanux.org \
--cc=stable@vger.kernel.org \
--cc=vdonnefort@gmail.com \
/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).