From: Mike Christie <michaelc@cs.wisc.edu>
To: open-iscsi@googlegroups.com
Cc: kxie@chelsio.com, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org, rranjan@chelsio.com,
James.Bottomley@HansenPartnership.com
Subject: Re: [PATCH 2/3] cxgb4i v5: iscsi driver
Date: Wed, 11 Aug 2010 13:37:31 -0500 [thread overview]
Message-ID: <4C62EDEB.3030007@cs.wisc.edu> (raw)
In-Reply-To: <201008091753.o79HrTmr020149@localhost.localdomain>
On 08/09/2010 12:53 PM, kxie@chelsio.com wrote:
> +
> +static void *t4_uld_add(const struct cxgb4_lld_info *lldi)
> +{
> + struct cxgbi_device *cdev;
> + struct port_info *pi;
> + int i, rc;
> +
> + cxgb4i_log_info("%s", version);
> +
> + cdev = cxgbi_device_register(sizeof(*lldi), lldi->nports);
> + if (!cdev) {
> + cxgb4i_log_info("t4 device 0x%p, register failed.\n", lldi);
> + return NULL;
> + }
> + cxgb4i_log_debug(1<< CXGBI_DBG_DEV,
> + "t4 0x%p,0x%x, ports %u,%s, chan %u, q %u,%u, wr %u.\n",
> + cdev, lldi->adapter_type, lldi->nports,
> + lldi->ports[0]->name, lldi->nchan, lldi->ntxq,
> + lldi->nrxq, lldi->wr_cred);
> + for (i = 0; i< lldi->nrxq; i++)
> + cxgb4i_log_debug(1<< CXGBI_DBG_DEV,
> + "t4 0x%p, rxq id #%d: %u.\n",
> + cdev, i, lldi->rxq_ids[i]);
> +
> + memcpy(cxgbi_cdev_priv(cdev), lldi, sizeof(*lldi));
> + cdev->flags = CXGBI_FLAG_DEV_T4;
> + cdev->pdev = lldi->pdev;
> + cdev->ports = lldi->ports;
> + cdev->nports = lldi->nports;
> + cdev->mtus = lldi->mtus;
> + cdev->nmtus = NMTUS;
> + cdev->snd_win = cxgb4i_snd_win;
> + cdev->rcv_win = cxgb4i_rcv_win;
> + cdev->rx_credit_thres = cxgb4i_rx_credit_thres;
> + cdev->skb_tx_rsvd = CXGB4I_TX_HEADER_LEN;
> + cdev->skb_rx_extra = sizeof(struct cpl_iscsi_hdr);
> + cdev->itp =&cxgb4i_iscsi_transport;
> +
> + rc = cxgbi_iscsi_init(cdev);
> + if (rc) {
> + cxgb4i_log_info("t4 0x%p iscsi init failed\n", cdev);
> + goto err_out;
> + }
For each LLD (cxgb3i and cxgb4i) could it get called more than once? I
mean if you had multiple cxgb3i HBAs could it get called once for each
or is it called just once time for all cxgb3i hbas? If more than once
the cxgbi_iscsi_init call to iscsi_register_transport would fail on the
second call, because the iscsi class would not allow you to register the
same transport twice.
next prev parent reply other threads:[~2010-08-11 18:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-09 17:53 [PATCH 2/3] cxgb4i v5: iscsi driver kxie-ut6Up61K2wZBDgjK7y7TUQ
2010-08-11 18:37 ` Mike Christie [this message]
2010-08-11 20:17 ` Karen Xie
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=4C62EDEB.3030007@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=James.Bottomley@HansenPartnership.com \
--cc=kxie@chelsio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=open-iscsi@googlegroups.com \
--cc=rranjan@chelsio.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