From: David Miller <davem@davemloft.net>
To: benli@broadcom.com
Cc: netdev@vger.kernel.org, mchan@broadcom.com, waie@broadcom.com
Subject: Re: [PATCH] cnic: Give a chance for the uio device to be opened before failing the path request
Date: Fri, 09 Apr 2010 15:49:45 -0700 (PDT) [thread overview]
Message-ID: <20100409.154945.118937724.davem@davemloft.net> (raw)
In-Reply-To: <1270762468-21128-1-git-send-email-benli@broadcom.com>
From: "Benjamin Li" <benli@broadcom.com>
Date: Thu, 8 Apr 2010 14:34:28 -0700
> There is a timing condition; where the time between the CNIC's
> /dev/uio* device registration and then the issuing of path requests
> messages is faster the brcm_iscsiuio daemon initializing.
>
> This can be seen if one sets the machine to automatically login into
> iSCSI targets. Then reset the network and iscsi daemons in quick
> succession. The login will fail because iscsid will only try
> a couple of times in quick succession. This patch will allow some
> additional needed time for the brcm_iscsiuio daemon to initialize
> before failing the path request call.
>
> Signed-off-by: Benjamin Li <benli@broadcom.com>
> Signed-off-by: Eddie Wai <waie@broadcom.com>
You need to create a proper serialization scheme to fix this.
Any delay value you choose is arbitrary, and could be easily exceeded
if swapping or other expensive operations are in propgress at the time
of the regristration.
Therefore all delay based schemes have a failure mode and therefore
isn't the way to fix this properly.
prev parent reply other threads:[~2010-04-09 22:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 21:34 [PATCH] cnic: Give a chance for the uio device to be opened before failing the path request Benjamin Li
2010-04-09 22:49 ` David Miller [this message]
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=20100409.154945.118937724.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=benli@broadcom.com \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=waie@broadcom.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).