From: Mike Christie <michaelc@cs.wisc.edu>
To: Jayamohan Kalickal <jayamohank@serverengines.com>
Cc: linux-scsi@vger.kernel.org,
Vikas Chaudhary <vikas.chaudhary@qlogic.com>,
Ravi Anand <ravi.anand@qlogic.com>
Subject: Re: [PATCH 1/1] be2iscsi: Enabling MSIX and mcc_rings V2
Date: Wed, 21 Oct 2009 12:39:58 -0500 [thread overview]
Message-ID: <4ADF476E.6000901@cs.wisc.edu> (raw)
In-Reply-To: <20091017011435.GA25197@serverengines.com>
Adding Qlogic guys on this one, because I think they want something similar.
Jayamohan Kallickal wrote:
> 4) Adds sysfs for FW commands
>
Jay, what operations are you wanting to do with the binary sysfs file?
Are there any operations that should be common with Qlogic?
Also if you guys both need binary operations for card specific
operations then binary sysfs is fine. However, James S had suggested
using bsg for this too. Since that is upstream now, and you could just
copy the FC implementation that might be a easier route (I think qlogic
might have mentioned sysfs was a pain sometimes, and it is something you
both could work on and help each other out on).
Comment on the implementation.
> MODULE_DEVICE_TABLE(pci, beiscsi_pci_id_table);
>
> +static ssize_t
> +beiscsi_sysfs_fw_wr(struct kobject *kobj, struct bin_attribute *bin_attr,
> + char *buf, loff_t off, size_t count) {
> +
> + unsigned int ret_len = 0;
> + struct Scsi_Host *shost = class_to_shost(container_of(kobj,
> + struct device, kobj));
> + struct beiscsi_hba *phba = iscsi_host_priv(shost);
> +
> + ret_len = mgmt_fw_cmd(&phba->ctrl, phba, buf, count);
For normal sysfs files I think we normally want it to do only one thing.
This one seems to be a cmd to exec and the data buffer. I am not sure if
that is right. Maybe you just want one file per operation. Or maybe you
want another file for the length of the opertaion so you do not have to
waste mem on that phba buffer.
Or JamesS's comment offlist about using the bsg pass through stuff is
also ok. Adding the infrastucture is a little more work, but it is
probably easier in the long run for the reasons he explained.
> + if (!ret_len) {
> + memcpy(buf, phba->attr_mem, count);
> + return count;
> + } else
> + return ret_len;
> +}
> +
> +static ssize_t
> +beiscsi_sysfs_fw_rd(struct kobject *kobj, struct bin_attribute *bin_attr,
> + char *buf, loff_t off, size_t count) {
> +
> + struct Scsi_Host *shost = class_to_shost(container_of(kobj,
> + struct device, kobj));
> + struct beiscsi_hba *phba = iscsi_host_priv(shost);
> +
> + memcpy(buf, phba->attr_mem, count);
> + return count;
> +}
> +
> +static struct bin_attribute sysfs_drvr_fw_prgrm_attr = {
> + .attr = {
> + .name = "be2iscsi_fw_prgrm",
> + .mode = S_IRUSR | S_IWUSR,
> + .owner = THIS_MODULE,
> + },
> + .size = 0,
> + .read = beiscsi_sysfs_fw_rd,
> + .write = beiscsi_sysfs_fw_wr,
> +};
> +
next prev parent reply other threads:[~2009-10-21 17:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-17 1:15 [PATCH 1/1] be2iscsi: Enabling MSIX and mcc_rings V2 Jayamohan Kallickal
2009-10-19 16:26 ` James Smart
2009-10-21 17:19 ` Mike Christie
2009-10-21 17:39 ` Mike Christie [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-10-21 18:10 Jayamohan Kalickal
2009-10-21 18:20 ` Mike Christie
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=4ADF476E.6000901@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=jayamohank@serverengines.com \
--cc=linux-scsi@vger.kernel.org \
--cc=ravi.anand@qlogic.com \
--cc=vikas.chaudhary@qlogic.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;
as well as URLs for NNTP newsgroup(s).