From: "Merav Sicron" <meravs@broadcom.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, eilong@broadcom.com,
"Merav Sicron" <meravs@broadcom.com>
Subject: [net-next patch 0/2] bnx2x: Enable cnic at run-time
Date: Wed, 7 Nov 2012 12:45:46 +0200 [thread overview]
Message-ID: <1352285148-21784-1-git-send-email-meravs@broadcom.com> (raw)
Hi Dave,
This patch series removes the BCM_CNIC bnx2x define, and eliminates the use of
the CONFIG_CNIC kconfig option.
The define removal is mainly important for SR-IOV, as the VF driver will use the
same code as the PF/hypervisor driver. Since storage is not supported in
SR-IOV (while is usually enabled in the non SR-IOV driver), we don't want to
waste resources on it.
After this change, cnic-related resources are allocated only when the cnic
module registers with bnx2x (which means that the user asked for storage
services). Also only at this stage the HW is configured to non-NIC (offload)
mode.
The first patch is the driver-FW HSI addition to change the 'update' ramrod for
offload mode configuration at run-time.
The second patch is for the removal of the BCM_CNIC define, and for separating
the load flow to two stages, one for L2 and one for cnic-related stuff.
Please consider applying this patch series to net-next.
Thanks,
Merav
next reply other threads:[~2012-11-07 7:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-07 10:45 Merav Sicron [this message]
2012-11-07 10:45 ` [net-next patch 1/2] bnx2x: HSI change for 'update' ramrod Merav Sicron
2012-11-07 10:45 ` [net-next patch 2/2] bnx2x: Support loading cnic resources at run-time Merav Sicron
2012-11-07 23:57 ` [net-next patch 0/2] bnx2x: Enable cnic " 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=1352285148-21784-1-git-send-email-meravs@broadcom.com \
--to=meravs@broadcom.com \
--cc=davem@davemloft.net \
--cc=eilong@broadcom.com \
--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).