On Oct 1, 2012, at 5:31 AM, Lalit Chandivade <lalit.chandiv...@qlogic.com> wrote:
> > >> -----Original Message----- >> From: Mike Christie [mailto:micha...@cs.wisc.edu] >> Sent: Tuesday, August 07, 2012 10:25 PM >> To: open-iscsi@googlegroups.com >> Cc: Lalit Chandivade; Ravi Anand; Vikas Chaudhary; Manish Rangankar >> Subject: Re: RFC: Doc: FLASH DDB Management using iscsiadm >> >> On 08/06/2012 06:27 AM, Lalit Chandivade wrote: >>> >>> >>>> -----Original Message----- >>>> From: Mike Christie [mailto:micha...@cs.wisc.edu] >>>> Sent: Friday, August 03, 2012 2:03 PM >>>> To: Lalit Chandivade >>>> Cc: open-iscsi@googlegroups.com; Ravi Anand; Vikas Chaudhary; Manish >>>> Rangankar >>>> Subject: Re: RFC: Doc: FLASH DDB Management using iscsiadm >>>> >>>> On 07/12/2012 05:37 PM, Lalit Chandivade wrote: >>>>> Hi Mike, >>>>> >>>>> We want to work on this solution that would enable qla4xxx users to >>>> manage the DDBs in FLASH and migrate the entries from FLASH to user >>>> space. >>>>> >>>>> Here is our initial thought, please review and let us know your feedback. >>>>> >>>> >>>> This sounds ok to me. Just some minor comments/questions that I am >>>> guessing you just glossed over to make it easier to understand. >>>> >>>> >>>>> Add support for FLASH DDB management in iscsiadm >>>>> ========================================= >>>>> >>>>> 1. Export normal target entries to /sys/class/iscsi_session from >>>>> FLASH when the driver comes up >>>>> /sys/class/iscsi_session/session2 <- for the DDB at Flash DDB index >>>>> 1 >>>>> /sys/class/iscsi_session/session3 <- for the DDB at Flash DDB index >>>>> 2 >>>>> /sys/class/iscsi_session/session4 <- for target at index 3 in the >>>>> RAM DDB >>>>> Note: This will need changes in the driver >>>> >>>> Are you are going to add a file on the session to indicate if it's >>>> flash or not or how can we tell? >>> >>> We already have the "creator" to differentiate. >>> /sys/class/iscsi_session/session1/creator >>> >>> Also we are thinking if we should add the FLASH DDBs under >>> /sys/firmware, something like >>> >>> /sys/firmware/iscsi_offload/host0/ >>> |-->iscsi_target/tgt0 >>> |-->iscsi_target/tgt0/iqn >>> |-->iscsi_target/tgt0/ip >>> |-->iscsi_target/tgt0/port >>> >>> As this will clearly distinguish between FLASH DDBs and user created node >> records. >>> >> >> This seems ok. > > Mike, > > After doing some initial work on this we have come up with following > directory structure and iscsiadm operations to manage the targets stored in > the HBAs flash. > Please review and let us know your comments. > > Display in Sysfs: > ================== > /sys/firmware/iscsi_offload/host1/new > /sys/firmware/iscsi_offload/host1/delete > /sys/firmware/iscsi_offload/host1/tgt0/logout > /sys/firmware/iscsi_offload/host1/tgt0/login > /sys/firmware/iscsi_offload/host1/tgt0/apply > /sys/firmware/iscsi_offload/host1/tgt0/<Target attributes> > > > Example: > /sys/firmware/iscsi_offload/host7/tgt1/address > /sys/firmware/iscsi_offload/host7/tgt1/default_time2retain > /sys/firmware/iscsi_offload/host7/tgt1/default_time2wait > /sys/firmware/iscsi_offload/host7/tgt1/firmware_cmd_timeout > /sys/firmware/iscsi_offload/host7/tgt1/first_burst_length > /sys/firmware/iscsi_offload/host7/tgt1/ipaddress > /sys/firmware/iscsi_offload/host7/tgt1/ip_options > /sys/firmware/iscsi_offload/host7/tgt1/iscsi_alias > /sys/firmware/iscsi_offload/host7/tgt1/iscsi_options > /sys/firmware/iscsi_offload/host7/tgt1/isid > /sys/firmware/iscsi_offload/host7/tgt1/is_persistent > /sys/firmware/iscsi_offload/host7/tgt1/login > /sys/firmware/iscsi_offload/host7/tgt1/logout > /sys/firmware/iscsi_offload/host7/tgt1/max_burst_length > /sys/firmware/iscsi_offload/host7/tgt1/max_outstanding_r2t > /sys/firmware/iscsi_offload/host7/tgt1/max_recv_data_segment_length > /sys/firmware/iscsi_offload/host7/tgt1/max_xmit_data_segment_length > /sys/firmware/iscsi_offload/host7/tgt1/name > /sys/firmware/iscsi_offload/host7/tgt1/noop_out_interval > /sys/firmware/iscsi_offload/host7/tgt1/port > /sys/firmware/iscsi_offload/host7/tgt1/target_options > /sys/firmware/iscsi_offload/host7/tgt1/tcp_options > /sys/firmware/iscsi_offload/host7/tgt1/tpgt > /sys/firmware/iscsi_offload/host7/tgt1/tsid > > Operations using iscsiadm: > ========================= > > List all targets stored in the FLASH of the HBA > > # iscsiadm -m host -H hostno -C target -o show What does -C stand for (why can't you use the existing -T)? Looks ok though. Sorry for the late response on this. Please in the future feel free to bug the heck out of me. Send me weekly reminders if needed. -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
