From: Sunil Kovvuri <sunil.kovvuri@gmail.com>
To: Pavel Fedin <p.fedin@samsung.com>
Cc: Linux Netdev List <netdev@vger.kernel.org>,
Sunil Goutham <sgoutham@cavium.com>,
Robert Richter <rric@kernel.org>,
youngmin.lee@cavium.com, kin-yip.liu@cavium.com
Subject: Re: [PATCH] net: thunderx: Remove unnecessary struct nicpf::lmac_cnt
Date: Fri, 4 Dec 2015 23:11:00 +0530 [thread overview]
Message-ID: <CA+sq2CejiQ1En32_26=Ub6haNgAW2HaKAMPpgVCMCds5ny1VcQ@mail.gmail.com> (raw)
In-Reply-To: <1449242242-9036-1-git-send-email-p.fedin@samsung.com>
>num_vf_en and lmac_cnt are always equal.However in future this may change.
Yes these two won't be equal in future and hence a differentiation is needed.
lmac_cnt will have to point to no of physical interfaces and num_vf_en
to logical interfaces.
num_vf_en will default to lmac_cnt but with 'sriov_configure' can be increased.
>The worst consequence of this is failure to deliver link status
> messages, causing VFs to go defunct
There is no point in delivering link status to all VFs, as
irrespective of physical link
status, VFs (attached to VMs) should be able to communicate. A
differentiation here
will also be needed then.
- for (vf = 0; vf < nic->lmac_cnt; vf++) {
+ for (vf = 0; vf < nic->num_vf_en; vf++) {
This is incorrect, if in future this refers to logical interfaces
which may be greater than
physical interface count then below references will fail.
/* Get BGX, LMAC indices for the VF */
bgx = NIC_GET_BGX_FROM_VF_LMAC_MAP(nic->vf_lmac_map[vf]);
lmac = NIC_GET_LMAC_FROM_VF_LMAC_MAP(nic->vf_lmac_map[vf]);
Thanks,
Sunil.
prev parent reply other threads:[~2015-12-04 17:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 15:17 [PATCH] net: thunderx: Remove unnecessary struct nicpf::lmac_cnt Pavel Fedin
2015-12-04 17:41 ` Sunil Kovvuri [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='CA+sq2CejiQ1En32_26=Ub6haNgAW2HaKAMPpgVCMCds5ny1VcQ@mail.gmail.com' \
--to=sunil.kovvuri@gmail.com \
--cc=kin-yip.liu@cavium.com \
--cc=netdev@vger.kernel.org \
--cc=p.fedin@samsung.com \
--cc=rric@kernel.org \
--cc=sgoutham@cavium.com \
--cc=youngmin.lee@cavium.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).