From: Johannes Thumshirn <jthumshirn@suse.de>
To: Arun Easi <arun.easi@cavium.com>
Cc: manish.rangankar@cavium.com, lduncan@suse.com, cleech@redhat.com,
martin.petersen@oracle.com, jejb@linux.vnet.ibm.com,
linux-scsi@vger.kernel.org, netdev@vger.kernel.org,
Yuval.Mintz@cavium.com, QLogic-Storage-Upstream@cavium.com,
Yuval Mintz <Yuval.Mintz@qlogic.com>
Subject: Re: [RFC 1/6] qed: Add support for hardware offloaded iSCSI.
Date: Thu, 20 Oct 2016 09:09:01 +0200 [thread overview]
Message-ID: <20161020070901.52tm2d255dquocho@linux-x5ow.site> (raw)
In-Reply-To: <alpine.LRH.2.00.1610191538530.25712@mvluser05.qlc.com>
Hi Arun,
On Wed, Oct 19, 2016 at 05:14:59PM -0700, Arun Easi wrote:
> Thanks Johannes for the review, please see my response below.
>
[...]
> >
> > Why not introduce a small helper like:
> > static inline bool qed_is_iscsi_personality()
> > {
> > return IS_ENABLED(CONFIG_QEDI) && p_hwfn->hw_info.personality ==
> > QED_PCI_ISCSI;
> > }
>
> I think I can remove the IS_ENABLED() check in places like this
> and have the check contained in header file. qed_iscsi_free()
> already is taken care, if I do the same fore qed_ooo*, I think
> the check would just be "p_hwfn->hw_info.personality ==
> QED_PCI_ISCSI", which would keep it consistent with the other
> areas where similar check is done for other protocols.
Sounds good.
>
[...]
> >
> > Is there any chance you could factor out above blocks into own functions so
> > you have
> >
> >
> > if (!GET_FIELD(p_ramrod->iscsi.flags,
> > ISCSI_CONN_OFFLOAD_PARAMS_TCP_ON_CHIP_1B)) {
> > qedi_do_stuff_off_chip();
> > else
> > qedi_do_stuff_on_chip();
> >
>
> This function mostly fills data needed for the firmware interface.
> By having all data necessary for the command
> ISCSI_RAMROD_CMD_ID_OFFLOAD_CONN in this function it is easier to
> refer what is being fed to firmware. If you do not have strong
> objections, I would like to keep it this way.
No strong objections, I just don't think these lengthy blocks are readable,
but I don't want to do too much bikeshedding about it.
Thanks,
Johannes
--
Johannes Thumshirn Storage
jthumshirn@suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
next prev parent reply other threads:[~2016-10-20 7:09 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 5:01 [RFC 0/6] Add QLogic FastLinQ iSCSI (qedi) driver manish.rangankar
2016-10-19 5:01 ` [RFC 1/6] qed: Add support for hardware offloaded iSCSI manish.rangankar
2016-10-19 7:31 ` Hannes Reinecke
2016-10-19 22:28 ` Arun Easi
2016-10-19 9:09 ` Johannes Thumshirn
2016-10-20 0:14 ` Arun Easi
2016-10-20 7:09 ` Johannes Thumshirn [this message]
2016-10-19 5:01 ` [RFC 2/6] qed: Add iSCSI out of order packet handling manish.rangankar
2016-10-19 7:36 ` Hannes Reinecke
2016-10-20 12:58 ` Mintz, Yuval
2016-10-19 9:39 ` Johannes Thumshirn
2016-10-20 0:43 ` Arun Easi
2016-10-19 5:01 ` [RFC 3/6] qedi: Add QLogic FastLinQ offload iSCSI driver framework manish.rangankar
2016-10-19 7:45 ` Hannes Reinecke
2016-10-20 8:27 ` Rangankar, Manish
2016-10-19 10:02 ` Johannes Thumshirn
2016-10-20 8:41 ` Rangankar, Manish
2016-10-23 14:04 ` Rangankar, Manish
2016-10-19 5:01 ` [RFC 4/6] qedi: Add LL2 iSCSI interface for offload iSCSI manish.rangankar
2016-10-19 7:53 ` Hannes Reinecke
2016-10-19 5:01 ` [RFC 5/6] qedi: Add support for iSCSI session management manish.rangankar
2016-10-19 8:03 ` Hannes Reinecke
2016-10-20 9:09 ` Rangankar, Manish
2016-10-19 13:28 ` Johannes Thumshirn
2016-10-20 9:12 ` Rangankar, Manish
2016-10-19 5:01 ` [RFC 6/6] qedi: Add support for data path manish.rangankar
2016-10-19 10:24 ` Hannes Reinecke
2016-10-20 9:24 ` Rangankar, Manish
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=20161020070901.52tm2d255dquocho@linux-x5ow.site \
--to=jthumshirn@suse.de \
--cc=QLogic-Storage-Upstream@cavium.com \
--cc=Yuval.Mintz@cavium.com \
--cc=Yuval.Mintz@qlogic.com \
--cc=arun.easi@cavium.com \
--cc=cleech@redhat.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=lduncan@suse.com \
--cc=linux-scsi@vger.kernel.org \
--cc=manish.rangankar@cavium.com \
--cc=martin.petersen@oracle.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).