All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saurav Kashyap <skashyap@marvell.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: GR-QLogic-Storage-Upstream
	<GR-QLogic-Storage-Upstream@marvell.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	Javed Hasan <jhasan@marvell.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: RE: [EXT] Re: [PATCH v3 1/7] qedf: Keep track of num of pending flogi.
Date: Tue, 14 Apr 2020 04:13:47 +0000	[thread overview]
Message-ID: <MN2PR18MB25278CD165DE5510B37846A9D2DA0@MN2PR18MB2527.namprd18.prod.outlook.com> (raw)
In-Reply-To: <yq17dyivp79.fsf@oracle.com>

Hi Martin,

> -----Original Message-----
> From: Martin K. Petersen <martin.petersen@oracle.com>
> Sent: Tuesday, April 14, 2020 6:50 AM
> To: Saurav Kashyap <skashyap@marvell.com>
> Cc: martin.petersen@oracle.com; GR-QLogic-Storage-Upstream <GR-QLogic-
> Storage-Upstream@marvell.com>; linux-scsi@vger.kernel.org; Javed Hasan
> <jhasan@marvell.com>; netdev@vger.kernel.org
> Subject: [EXT] Re: [PATCH v3 1/7] qedf: Keep track of num of pending flogi.
> 
> External Email
> 
> ----------------------------------------------------------------------
> 
> Saurav,
> 
> Please, no "." at the end of Subject: lines.
> 
> > - Problem: Port not coming up after bringing down the port
> >   for longer duration.
> > - Bring down the port from the switch
> > - wait for fipvlan to exhaust, driver will use
> >   default vlan (1002) and call fcoe_ctlr_link_up
> > - libfc/fcoe will start sending FLOGI
> > - bring back the port and switch discard FLOGI
> >   because vlan is different.
> > - keep track of pending flogi and if it increases
> >   certain number then do ctx reset and it will do
> >   fipvlan again.
> 
> That doesn't look like a proper commit message.
> 
> How about something like:
> 
>     If a port is brought down for an extended period of time, the
>     fipvlan counter gets exhausted and the driver will fall back to
>     default VLAN 1002 and call fcoe_ctlr_link_up to log in. However, the
>     switch will discard the FLOGI attempt because the VLAN is now
>     different.
> 
>     Keep track of the number of FLOGI attempts and if a threshold of
>     QEDF_FLOGI_RETRY_CNT is exceeded, perform a context soft reset.

<SK> Looks good.

Thanks,
~Saurav
> 
> --
> Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2020-04-14  4:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-03 12:09 [PATCH v3 0/7] qed/qedf: Firmware recovery, bw update and misc fixes Saurav Kashyap
2020-04-03 12:09 ` [PATCH v3 1/7] qedf: Keep track of num of pending flogi Saurav Kashyap
2020-04-14  1:19   ` Martin K. Petersen
2020-04-14  4:13     ` Saurav Kashyap [this message]
2020-04-03 12:09 ` [PATCH v3 2/7] qedf: Fix for the deviations from the SAM-4 spec Saurav Kashyap
2020-04-14  1:22   ` Martin K. Petersen
2020-04-14  4:20     ` [EXT] " Saurav Kashyap
2020-04-03 12:09 ` [PATCH v3 3/7] qed: Send BW update notifications to the protocol drivers Saurav Kashyap
2020-04-03 12:09 ` [PATCH v3 4/7] qedf: Implement callback for bw_update Saurav Kashyap
2020-04-14  1:24   ` Martin K. Petersen
2020-04-14  4:18     ` [EXT] " Saurav Kashyap
2020-04-03 12:09 ` [PATCH v3 5/7] qedf: Add schedule recovery handler Saurav Kashyap
2020-04-14  1:25   ` Martin K. Petersen
2020-04-03 12:09 ` [PATCH v3 6/7] qedf: Fix crash when MFW calls for protocol stats while function is still probing Saurav Kashyap
2020-04-03 12:09 ` [PATCH v3 7/7] qedf: Get dev info after updating the params Saurav Kashyap
2020-04-14  1:27   ` Martin K. Petersen
2020-04-14  4:21     ` [EXT] " Saurav Kashyap

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=MN2PR18MB25278CD165DE5510B37846A9D2DA0@MN2PR18MB2527.namprd18.prod.outlook.com \
    --to=skashyap@marvell.com \
    --cc=GR-QLogic-Storage-Upstream@marvell.com \
    --cc=jhasan@marvell.com \
    --cc=linux-scsi@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.