public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Ravi Anand <ravi.anand@qlogic.com>
To: Mike Christie <michaelc@cs.wisc.edu>
Cc: James Bottomley <james.bottomley@suse.de>,
	Linux-SCSI Mailing List <linux-scsi@vger.kernel.org>,
	Vikas Chaudhary <vikas.chaudhary@qlogic.com>
Subject: Re: [PATCH 02/11] qla4xxx: added IPv6 support.
Date: Thu, 11 Feb 2010 03:09:10 -0800	[thread overview]
Message-ID: <20100211110910.GD8237@linux-qf4p> (raw)
In-Reply-To: <4B671A34.9080300@cs.wisc.edu>

On Mon, 01 Feb 2010, Mike Christie wrote:
> On 01/30/2010 12:28 AM, Ravi Anand wrote:
> > +       uint16_t iscsi_max_burst_len;
> > +       uint16_t iscsi_max_outsnd_r2t;
> > +       uint16_t iscsi_first_burst_len;
> > +       uint16_t iscsi_max_rcv_data_seg_len;
> > +       uint16_t iscsi_max_snd_data_seg_len;
> 
> 
> Probably do not need those settings above. Did not really see them used.

Sorry for the late reply as I was sick. 

Currently we are caching it in the DDB struct from the F/W database
and the goal is to export it to user space.
> 
> 
> 
> > +
> > +       struct in6_addr remote_ipv6_addr;
> > +       struct in6_addr link_local_ipv6_addr;
> >   };
> >
> >   /*
> > @@ -275,6 +284,16 @@ struct ddb_entry {
> >   #include "ql4_fw.h"
> >   #include "ql4_nvram.h"
> >
> > +/* shortcut to print ISID */
> > +#define ISID(addr) \
> > +       ((unsigned char *)&addr)[5], \
> > +       ((unsigned char *)&addr)[4], \
> > +       ((unsigned char *)&addr)[3], \
> > +       ((unsigned char *)&addr)[2], \
> > +       ((unsigned char *)&addr)[1], \
> > +       ((unsigned char *)&addr)[0]
> > +#define ISID_FMT "0x%02x%02x%02x%02x%02x%02x"
> 
> 
> Also not used. And if you add it, it should go in iscsi_proto.h.

We will remvoe it. 
> 
> 
> > +       DEBUG2(dev_info(&ha->pdev->dev, "%s: DDB[%d] osIdx = %d "
> > +                                       "State %04x ConnErr %08x "
> > +                                       NIPQUAD_FMT ":%04d \"%s\"\n",
> 
> 
> Do you go down this path for ipv6 (looked like it did and did in other 
> places)?

IPV4 and IPV6.

> NIPQUAD_FMT will not work, and we are trying to not use it 
> NIPQUAD_FMT/NIPQUAD. See %pI4 use in qla4xxx_conn_get_param. There is 
> also a %pI6 for ipv6.

OK. We will modify it to use %pI4 or %pI4.
> 
> Also you need to update qla4xxx_conn_get_param and 
> qla4xxx_host_get_param ip handling.

Will do. Missed it.
> 
> 
> > +       if (qla4xxx_mailbox_command(ha, 6, 6, mbox_cmd, mbox_sts)
> > +               != QLA_SUCCESS) {
> 
> 
> I think we normally put the != on the end of the other line.

OK.

Thanks
Ravi

  reply	other threads:[~2010-02-11 11:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-30  6:28 [PATCH 02/11] qla4xxx: added IPv6 support Ravi Anand
2010-02-01 18:15 ` Mike Christie
2010-02-11 11:09   ` Ravi Anand [this message]
     [not found]   ` <7312FDA8-2587-4DA7-9762-978EA46A8B9C@qlogic.com>
2010-04-07  3:43     ` Mike Christie
2010-04-07  5:46       ` Karen Xie
2010-04-07 17:41       ` Mike Christie
  -- strict thread matches above, loose matches on Subject: below --
2010-04-07 17:26 Jayamohan Kalickal
2010-04-07 18:00 ` 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=20100211110910.GD8237@linux-qf4p \
    --to=ravi.anand@qlogic.com \
    --cc=james.bottomley@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    --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