From: David L Stevens <david.stevens@oracle.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCHv3 net-next 1/3] sunvnet: upgrade to VIO protocol version 1.6
Date: Sat, 13 Sep 2014 22:39:25 -0400 [thread overview]
Message-ID: <5414FFDD.9050509@oracle.com> (raw)
In-Reply-To: <20140913.161842.2265200935397549583.davem@davemloft.net>
On 09/13/2014 04:18 PM, David Miller wrote:
> From: David L Stevens <david.stevens@oracle.com>
> Is this really applicable to devices other than sunvnet? Just keep
> this attribute in the sunvnet driver "struct vnet_port" private state.
Yes, I'll move it.
>
>> + /* v1.6 and higher, ACK with desired, supported mode, or NACK */
>> + if (vio->ver.major <= 1 && vio->ver.minor >= 6) {
> ...
>> + if (vio->ver.major <= 1 && vio->ver.minor < 2)
> ...
>> + /* for version < 1.2, VIO_DRING_MODE = 0x3 and no bitmask */
>> + if ((vio->ver.major <= 1 && vio->ver.minor < 2) &&
> ...
>> + if (vio->ver.major == 1 && vio->ver.minor < 3) {
> ...
>> + } else if (vio->ver.major == 1 && vio->ver.minor == 3) {
> ...
>> + } else {
> ...
>> + }
> ...
>> + /* for version >= 1.6, ACK packet mode we support */
>> + if (vio->ver.major <= 1 && vio->ver.minor >= 6) {
>
> These version tests give me a headache, and some of them accept
> impossible things like major version zero. If we only have major
> version 1 and later in our version lists, testing things like "major
> <= 1" makes no sense at all.
>
> That last test quoted above definitely looks wrong, it should
> be testing "major >= 1" if anything if it is trying to test
> "version >= 1.6"
Yes, that'd break at > v2.0 -- good catch.
> Sadly, I expect that we'll have more and more of these version tests
> over time. So why not make some generic helpers in the VIO or LDC
> layer?
>
> static inline bool vio_version_before(struct vio_driver_state *vio,
> u16 major, u16 minor)
> {
> u32 have = (u32)vio->major << 16 | vio->minor;
> u32 want = (u32)major << 16 | minor;
>
> return have < want;
> }
> static inline bool vio_version_after_eq(struct vio_driver_state *vio,
> u16 major, u16 minor)
> {
> u32 have = (u32)vio->major << 16 | vio->minor;
> u32 want = (u32)major << 16 | minor;
>
> return have >= want;
> }
>
> Something like that.
Sure. I was thinking about something like:
#define VIO_VER(major, minor) (((major)<<16)|(minor))
change the version struct to a 32-bit int, and do things like:
if (vio->ver > VIO_VER(1,6)) {
unless you have a preference. (?)
+-DLS
next prev parent reply other threads:[~2014-09-14 2:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-13 16:01 [PATCHv3 net-next 1/3] sunvnet: upgrade to VIO protocol version 1.6 David L Stevens
2014-09-13 20:18 ` David Miller
2014-09-14 2:39 ` David L Stevens [this message]
2014-09-14 3:01 ` David Miller
2014-09-14 3:43 ` Raghuram Kothakota
2014-09-14 3:30 ` Raghuram Kothakota
2014-09-14 12:02 ` David L Stevens
2014-09-14 17:21 ` Raghuram Kothakota
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=5414FFDD.9050509@oracle.com \
--to=david.stevens@oracle.com \
--cc=davem@davemloft.net \
--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 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.