From: Arun Easi <arun.easi@cavium.com>
To: Hannes Reinecke <hare@suse.de>
Cc: "Dupuis, Chad" <chad.dupuis@cavium.com>,
<martin.petersen@oracle.com>, <linux-scsi@vger.kernel.org>,
<fcoe-devel@open-fcoe.org>, <netdev@vger.kernel.org>,
<yuval.mintz@cavium.com>, <QLogic-Storage-Upstream@cavium.com>
Subject: Re: [PATCH V2 net-next 1/2] qed: Add support for hardware offloaded FCoE.
Date: Mon, 30 Jan 2017 10:53:16 -0800 [thread overview]
Message-ID: <alpine.LRH.2.00.1701301035450.7335@mvluser05.qlc.com> (raw)
In-Reply-To: <bdcd89cf-85cc-5eb9-d3b1-d42bbb34c973@suse.de>
On Mon, 30 Jan 2017, 1:44am, Hannes Reinecke wrote:
> On 01/25/2017 09:33 PM, Dupuis, Chad wrote:
> > From: Arun Easi <arun.easi@qlogic.com>
> >
> > This adds the backbone required for the various HW initalizations
> > which are necessary for the FCoE driver (qedf) for QLogic FastLinQ
> > 4xxxx line of adapters - FW notification, resource initializations, etc.
> >
> > Signed-off-by: Arun Easi <arun.easi@cavium.com>
> > Signed-off-by: Yuval Mintz <yuval.mintz@cavium.com>
> > ---
> > drivers/net/ethernet/qlogic/Kconfig | 3 +
> > drivers/net/ethernet/qlogic/qed/Makefile | 1 +
> > drivers/net/ethernet/qlogic/qed/qed.h | 11 +
> > drivers/net/ethernet/qlogic/qed/qed_cxt.c | 98 ++-
> > drivers/net/ethernet/qlogic/qed/qed_cxt.h | 3 +
> > drivers/net/ethernet/qlogic/qed/qed_dcbx.c | 13 +-
> > drivers/net/ethernet/qlogic/qed/qed_dcbx.h | 5 +-
> > drivers/net/ethernet/qlogic/qed/qed_dev.c | 205 ++++-
> > drivers/net/ethernet/qlogic/qed/qed_dev_api.h | 42 +
> > drivers/net/ethernet/qlogic/qed/qed_fcoe.c | 990 ++++++++++++++++++++++
> > drivers/net/ethernet/qlogic/qed/qed_fcoe.h | 52 ++
> > drivers/net/ethernet/qlogic/qed/qed_hsi.h | 781 ++++++++++++++++-
> > drivers/net/ethernet/qlogic/qed/qed_hw.c | 3 +
> > drivers/net/ethernet/qlogic/qed/qed_ll2.c | 25 +
> > drivers/net/ethernet/qlogic/qed/qed_ll2.h | 2 +-
> > drivers/net/ethernet/qlogic/qed/qed_main.c | 7 +
> > drivers/net/ethernet/qlogic/qed/qed_mcp.c | 3 +
> > drivers/net/ethernet/qlogic/qed/qed_mcp.h | 1 +
> > drivers/net/ethernet/qlogic/qed/qed_reg_addr.h | 8 +
> > drivers/net/ethernet/qlogic/qed/qed_sp.h | 4 +
> > drivers/net/ethernet/qlogic/qed/qed_sp_commands.c | 3 +
> > include/linux/qed/common_hsi.h | 10 +-
> > include/linux/qed/fcoe_common.h | 715 ++++++++++++++++
> > include/linux/qed/qed_fcoe_if.h | 145 ++++
> > include/linux/qed/qed_if.h | 41 +-
> > 25 files changed, 3152 insertions(+), 19 deletions(-)
> > create mode 100644 drivers/net/ethernet/qlogic/qed/qed_fcoe.c
> > create mode 100644 drivers/net/ethernet/qlogic/qed/qed_fcoe.h
> > create mode 100644 include/linux/qed/fcoe_common.h
> > create mode 100644 include/linux/qed/qed_fcoe_if.h
> >
> [ .. ]
> > diff --git a/drivers/net/ethernet/qlogic/qed/qed_dcbx.h b/drivers/net/ethernet/qlogic/qed/qed_dcbx.h
> > index d70300f..0fabe97 100644
> > --- a/drivers/net/ethernet/qlogic/qed/qed_dcbx.h
> > +++ b/drivers/net/ethernet/qlogic/qed/qed_dcbx.h
> > @@ -57,7 +57,6 @@ struct qed_dcbx_app_data {
> > u8 tc; /* Traffic Class */
> > };
> >
> > -#ifdef CONFIG_DCB
> > #define QED_DCBX_VERSION_DISABLED 0
> > #define QED_DCBX_VERSION_IEEE 1
> > #define QED_DCBX_VERSION_CEE 2
> > @@ -73,7 +72,6 @@ struct qed_dcbx_set {
> > struct qed_dcbx_admin_params config;
> > u32 ver_num;
> > };
> > -#endif
> >
> > struct qed_dcbx_results {
> > bool dcbx_enabled;
> > @@ -97,9 +95,8 @@ struct qed_dcbx_info {
> > struct qed_dcbx_results results;
> > struct dcbx_mib operational;
> > struct dcbx_mib remote;
> > -#ifdef CONFIG_DCB
> > struct qed_dcbx_set set;
> > -#endif
> > + struct qed_dcbx_get get;
> > u8 dcbx_cap;
> > };
> >
> Why did you remove the dependency on 'CONFIG_DCB'?
Thanks Hannes for the review.
The offloaded functions are not dependent on CONFIG_DCB; the DCB
functionality is handled by the firmware for them. The above '#ifdef'-ed
part is shared by offloaded functions, and should be present regardless of
the CONFIG_DCB setting.
Regards,
-Arun
>
> Other than that:
>
> Reviewed-by: Hannes Reinecke <hare@suse.com>
next prev parent reply other threads:[~2017-01-30 18:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 20:33 [PATCH V2 0/2] Add QLogic FastLinQ FCoE (qedf) driver Dupuis, Chad
2017-01-25 20:33 ` [PATCH V2 net-next 1/2] qed: Add support for hardware offloaded FCoE Dupuis, Chad
[not found] ` <1485376423-18737-2-git-send-email-chad.dupuis-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>
2017-01-30 9:44 ` Hannes Reinecke
2017-01-30 18:53 ` Arun Easi [this message]
2017-01-25 20:33 ` [PATCH V2 2/2] qedf: Add QLogic FastLinQ offload FCoE driver framework Dupuis, Chad
2017-01-25 21:53 ` kbuild test robot
[not found] ` <1485376423-18737-3-git-send-email-chad.dupuis-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>
2017-01-30 10:34 ` Hannes Reinecke
[not found] ` <28df9087-4eaf-d72c-ccee-89408d3a1b32-l3A5Bk7waGM@public.gmane.org>
2017-01-31 17:08 ` Chad Dupuis
[not found] ` <alpine.OSX.2.00.1701311156290.1169-nVgGmETfwnIFUnR/tdpssI0aTaFgKE92ACYyPGjX6YU@public.gmane.org>
2017-02-01 7:59 ` Hannes Reinecke
2017-01-31 18:38 ` Chad Dupuis
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=alpine.LRH.2.00.1701301035450.7335@mvluser05.qlc.com \
--to=arun.easi@cavium.com \
--cc=QLogic-Storage-Upstream@cavium.com \
--cc=chad.dupuis@cavium.com \
--cc=fcoe-devel@open-fcoe.org \
--cc=hare@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=netdev@vger.kernel.org \
--cc=yuval.mintz@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