From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Arkady Gilinsky <arkady.gilinsky@harmonicinc.com>,
"Creeley, Brett" <brett.creeley@intel.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: Arkady Gilinsky <arcadyg@gmail.com>
Subject: Re: [EXTERNAL] RE: [PATCH net] i40e/iavf: Fix msg interface between VF and PF
Date: Thu, 07 Nov 2019 11:38:55 -0800 [thread overview]
Message-ID: <d078d3efc784805a67ba1a1c6e94fb4ec1c0aec6.camel@intel.com> (raw)
In-Reply-To: <1573018214.10368.1.camel@harmonicinc.com>
[-- Attachment #1: Type: text/plain, Size: 2900 bytes --]
On Wed, 2019-11-06 at 05:30 +0000, Arkady Gilinsky wrote:
> On Tue, 2019-11-05 at 16:55 +0000, Creeley, Brett wrote:
> > > -----Original Message-----
> > > From: Arkady Gilinsky <arkady.gilinsky@harmonicinc.com>
> > > Sent: Monday, November 4, 2019 9:24 PM
> > > To: Creeley, Brett <brett.creeley@intel.com>;
> > > intel-wired-lan@lists.osuosl.org; netdev@vger.kernel.org; Kirsher,
> > > Jeffrey T
> > > <jeffrey.t.kirsher@intel.com>
> > > Cc: Arkady Gilinsky <arcadyg@gmail.com>
> > > Subject: Re: [EXTERNAL] RE: [PATCH net] i40e/iavf: Fix msg interface
> > > between VF and PF
> > > > static bool i40e_vc_verify_vqs_bitmaps(struct virtchnl_queue_select
> > > > *vqs)
> > > > {
> > > > /* this will catch any changes made to the virtchnl_queue_select
> > > > bitmap */
> > > > if (sizeof(vqs->rx_queues) != sizeof(u32) ||
> > > > sizeof(vqs->tx_queues) != sizeof(u32))
> > > > return false;
> > >
> > > If so, then is it better to check the type of the fields in compile-
> > > time rather than in runtime ?
> > > Something like this:
> > > BUILD_BUG_ON(sizeof(vqs->rx_queues) != sizeof(u32));
> > > BUILD_BUG_ON(sizeof(vqs->tx_queues) != sizeof(u32));
> > > This is not required comparison each time when function is called and
> > > made code more optimized.
> >
> > I don't think this is required with the change you suggested below.
> Agree.
> If other code in driver not need to be adjusted/verified, then this check
> is not needed.
> > > > if ((vqs->rx_queues == 0 && vqs->tx_queues == 0) ||
> > > > hweight32(vqs->rx_queues) > I40E_MAX_VF_QUEUES ||
> > > > hweight32(vqs->tx_queues) > I40E_MAX_VF_QUEUES)
> > > > return false;
> > >
> > > Again, from optimization POV it is better to have constant changed
> > > than variable,
> > > since it is compile time and not run time action:
> > > if ((vqs->rx_queues == 0 && vqs->tx_queues == 0) ||
> > > vqs->rx_queues >= (BIT(I40E_MAX_VF_QUEUES)) ||
> > >
> > > vqs->tx_queues >= (BIT(I40E_MAX_VF_QUEUES)))
> > > return false;
> >
> > This seems much better than my solution. It fixes the original issue,
> > handles if the
> > vqs->[r|t]x_queues variables have changed in size, and the queue bitmap
> > comparison
> > uses a constant. Thanks!
> Thanks to you for feedback.
> I am trying to understand if this patch will enter into official kernel
> tree
> and, not less important from my POV, to official Intel drivers.
> Brett/Jeffrey, could you, please, assist to make sure that this fix, or
> fix suggested by Brett,
> will be integrated into Intel i40e/iavf drivers ?
> Or may be I should write mail straight to Intel support ?
As Brett pointed out, there are issues with this patch. Please make the
suggested changes and re-submit the patch to
intel-wired-lan@lists.osuosl.org
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-11-07 19:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 5:32 [PATCH net] i40e/iavf: Fix msg interface between VF and PF Arkady Gilinsky
2019-11-04 23:43 ` Creeley, Brett
2019-11-05 5:23 ` [EXTERNAL] " Arkady Gilinsky
2019-11-05 16:55 ` Creeley, Brett
2019-11-06 5:30 ` Arkady Gilinsky
2019-11-07 19:38 ` Jeff Kirsher [this message]
2019-11-08 16:43 ` Creeley, Brett
2019-11-12 7:33 ` Arkady Gilinsky
2019-11-13 18:47 ` Jeff Kirsher
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=d078d3efc784805a67ba1a1c6e94fb4ec1c0aec6.camel@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=arcadyg@gmail.com \
--cc=arkady.gilinsky@harmonicinc.com \
--cc=brett.creeley@intel.com \
--cc=intel-wired-lan@lists.osuosl.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).