From: Eddie Williams <Eddie.Williams@steeleye.com>
To: Doug Ledford <dledford@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Linux Cluster using shared scsi
Date: Fri, 04 May 2001 10:52:18 -0400 [thread overview]
Message-ID: <200105041452.f44EqI101653@localhost.localdomain> (raw)
In-Reply-To: Message from Doug Ledford <dledford@redhat.com> of "Wed, 02 May 2001 13:47:40 EDT." <3AF0483C.49C8CF90@redhat.com>
Doug Ledford wrote:
>
> ...
>
> If told to hold a reservation, then resend your reservation request once every
> 2 seconds (this actually has very minimal CPU/BUS usage and isn't as big a
> deal as requesting a reservation every 2 seconds might sound). The first time
> the reservation is refused, consider the reservation stolen by another machine
> and exit (or optionally, reboot).
I agree that the resend of the reservation is not all that big but there is
also the proverbial "straw that broke the Camel's back." When there is enough
activity there could be logic added to avoid sending reservations. In all
cases when a reservation is forcefully removed the result will cause the
device to return a UNIT ATTENTION (Well, I guess I know that is the behavior
on Parallel SCSI, is this true for FC?). So the host should know with the
next command issued that it lost the reservation (not necessarily that someone
else has stolen it but that for some reason the device just lost it). So you
could "check" to see if within the last 2 seconds (a) has an IO completed and
(b) every IO that completed in that 2 second span completed without any
"error". In error I mean without incident, such as a check condition. In
this case the reservation is not needed as you know nothing has happened to
cause the reservation to be lost. Perhaps in this heavy load situation you
could even add logic to issue the reservation as soon as the mid-layer is
aware that the reservation was broken maybe saving a second or so?
I see this as an enhancement that could be added on later, perhaps keep in
mind this enhancement so that your initial development does not make it more
difficult to implement it later.
Eddie
next prev parent reply other threads:[~2001-05-04 14:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-01 13:07 Roets, Chris
2001-05-01 14:45 ` James Bottomley
2001-05-01 16:10 ` Doug Ledford
2001-05-01 17:05 ` Eric Z. Ayers
2001-05-01 20:38 ` Alan Cox
2001-05-01 20:52 ` James Bottomley
2001-05-01 21:07 ` Eric Z. Ayers
2001-05-01 21:24 ` Alan Cox
2001-05-02 15:20 ` Doug Ledford
2001-05-02 16:37 ` Eddie Williams
2001-05-02 17:20 ` Mike Anderson
2001-05-02 17:50 ` Doug Ledford
2001-05-02 18:55 ` Mike Anderson
2001-05-02 20:31 ` Doug Ledford
2001-05-03 12:53 ` James Bottomley
2001-05-03 13:52 ` James Bottomley
2001-05-02 17:39 ` Max TenEyck Woodbury
2001-05-02 17:47 ` Doug Ledford
2001-05-02 21:03 ` Pavel Machek
2001-05-03 22:32 ` Jonathan Lundell
2001-05-02 21:47 ` Max TenEyck Woodbury
2001-05-02 23:16 ` Doug Ledford
2001-05-03 19:57 ` Eric Z. Ayers
2001-05-04 14:52 ` Eddie Williams [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-27 15:11 James Bottomley
2001-04-27 13:18 Roets, Chris
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=200105041452.f44EqI101653@localhost.localdomain \
--to=eddie.williams@steeleye.com \
--cc=dledford@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®