netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yuval Mintz <Yuval.Mintz@qlogic.com>
To: <davem@davemloft.net>, <netdev@vger.kernel.org>
Cc: Yuval Mintz <Yuval.Mintz@qlogic.com>
Subject: [PATCH net-next 0/6] qed: IOV series - relax firmware requirements
Date: Sun, 5 Jun 2016 13:11:10 +0300	[thread overview]
Message-ID: <1465121476-32494-1-git-send-email-Yuval.Mintz@qlogic.com> (raw)

In order for VFs to work, current implementation demands that the VF's
requried storm firmware would be exactly the version that was loaded by
the PF, which is a very harsh requirement.
This patch series is intended to relax this -
the recently submitted firmware is intended to be forward/backward
compatible in its fastpath [slowpath is configured by PF on behalf of VF],
and so VFs would only be required of having the same major faspath HSI in
order to work.

Most of the other patches in this series extend current forward
compatibilty of driver to reduce chance of breaking PF/VF compatibility
in the future. A few are unrelated IOV changes.

Dave,

Please consider applying these to 'net-next'.

Thanks,
Yuval

Yuval Mintz (6):
  qed: Relax VF firmware requirements
  qed: PF-VF resource negotiation
  qed: Make PF more robust against malicious VF
  qed: Move doorbell calculation from VF to PF
  qed: PF enforce MAC limitation of VFs
  qed: PF to reply to unknown messages

 drivers/net/ethernet/qlogic/qed/qed_sriov.c | 488 +++++++++++++++++++++-------
 drivers/net/ethernet/qlogic/qed/qed_sriov.h |   9 +-
 drivers/net/ethernet/qlogic/qed/qed_vf.c    |  95 ++++--
 drivers/net/ethernet/qlogic/qed/qed_vf.h    |  13 +-
 4 files changed, 456 insertions(+), 149 deletions(-)

-- 
1.9.3

             reply	other threads:[~2016-06-05 10:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-05 10:11 Yuval Mintz [this message]
2016-06-05 10:11 ` [PATCH net-next 1/6] qed: Relax VF firmware requirements Yuval Mintz
2016-06-05 10:11 ` [PATCH net-next 2/6] qed: PF-VF resource negotiation Yuval Mintz
2016-06-05 10:11 ` [PATCH net-next 3/6] qed: Make PF more robust against malicious VF Yuval Mintz
2016-06-05 10:11 ` [PATCH net-next 4/6] qed: Move doorbell calculation from VF to PF Yuval Mintz
2016-06-05 10:11 ` [PATCH net-next 5/6] qed: PF enforce MAC limitation of VFs Yuval Mintz
2016-06-05 10:11 ` [PATCH net-next 6/6] qed: PF to reply to unknown messages Yuval Mintz
2016-06-07 22:40 ` [PATCH net-next 0/6] qed: IOV series - relax firmware requirements David Miller

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=1465121476-32494-1-git-send-email-Yuval.Mintz@qlogic.com \
    --to=yuval.mintz@qlogic.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 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).