All of lore.kernel.org
 help / color / mirror / Atom feed
From: David L Stevens <david.stevens@oracle.com>
To: Raghuram Kothakota <Raghuram.Kothakota@oracle.com>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCHv6 net-next 1/3] sunvnet: upgrade to VIO protocol version 1.6
Date: Thu, 18 Sep 2014 09:21:31 -0400	[thread overview]
Message-ID: <541ADC5B.2080702@oracle.com> (raw)
In-Reply-To: <F34B8038-D189-4DD7-BF98-26CC4BD11990@oracle.com>



On 09/18/2014 12:23 AM, Raghuram Kothakota wrote:

>>
>> +	/* v1.6 and higher, ACK with desired, supported mode, or NACK */
>> +	if (vio_version_after_eq(vio, 1, 6)) {
>> +		if (!(pkt->options & VIO_TX_DRING))
>> +			goto send_nack;
>> +		pkt->options = VIO_TX_DRING;
>> +	}
>> +
> 
> 
> I forget to send this comment in my previous email. The above function is
> common to all clients, that includes vdisk.  The vdisk today doesn't use any
> version number above 1.2 or 1.3, so it probably won't impact it, but  this
> special handling doesn't seem to belong in the common code.

Yes, this is updating the VIO protocol, which is used by both sunvnet and sunvdc.
If the vdisk uses a newer protocol version, it will need to do exactly what this
code does (and it already will, because this code is there).

Any protocol version differences in the vdisk-specific code will need to be part
of a vdisk version upgrade patch. The particular VIO version that is negotiated
is specified in the individual drivers and my patches update that for sunvnet only.
The sunvdc code is still negotiating and using 1.0 in the net-next kernel, so
none of these version checks change anything for the sunvdc driver.

							+-DLS

      reply	other threads:[~2014-09-18 13:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-18  0:11 [PATCHv6 net-next 1/3] sunvnet: upgrade to VIO protocol version 1.6 David L Stevens
2014-09-18  4:09 ` Raghuram Kothakota
2014-09-18 13:03   ` David L Stevens
2014-09-18 18:49     ` Raghuram Kothakota
2014-09-18 19:58       ` David L Stevens
2014-09-22  4:40         ` David L Stevens
2014-09-22 16:40           ` Raghuram Kothakota
2014-09-23 16:24     ` David Miller
2014-09-23 16:49       ` David L Stevens
2014-09-23 18:44         ` David Miller
2014-09-24 14:43           ` David L Stevens
2014-09-18  4:23 ` Raghuram Kothakota
2014-09-18 13:21   ` David L Stevens [this message]

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=541ADC5B.2080702@oracle.com \
    --to=david.stevens@oracle.com \
    --cc=Raghuram.Kothakota@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.