From: Lars Marowsky-Bree <lmb@suse.de>
To: Tim Pepper <tpepper@gmail.com>,
device-mapper development <dm-devel@redhat.com>
Cc: tranlan@us.ibm.com, Linux SCSI <linux-scsi@vger.kernel.org>,
aherrman@de.ibm.com
Subject: Re: Re: fastfail operation and retries
Date: Tue, 3 May 2005 13:11:02 +0200 [thread overview]
Message-ID: <20050503111102.GJ1285@marowsky-bree.de> (raw)
In-Reply-To: <eada2a0705042715573dd04ab1@mail.gmail.com>
On 2005-04-27T15:57:09, Tim Pepper <tpepper@gmail.com> wrote:
> > User-space needs to take action and tell us when to stop queuing.
> Is there any risk of priority inversion?
That risk of course always exists (and it'd exist in the kernel too).
The code in question needs to be auditted to make sure this case is
taken care of.
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business -- Charles Darwin
"Ignorance more frequently begets confidence than does knowledge"
next prev parent reply other threads:[~2005-05-03 11:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 21:33 [dm-devel] Re: fastfail operation and retries Andreas Herrmann
2005-04-21 21:38 ` David S. Miller
2005-04-21 22:24 ` Lars Marowsky-Bree
2005-04-22 19:13 ` Lan
2005-04-25 23:56 ` [dm-devel] " Tim Pepper
2005-04-27 14:44 ` Lars Marowsky-Bree
2005-04-27 22:57 ` Tim Pepper
2005-05-03 11:11 ` Lars Marowsky-Bree [this message]
2005-04-26 9:55 ` Lars Marowsky-Bree
-- strict thread matches above, loose matches on Subject: below --
2005-04-21 22:01 goggin, edward
2005-04-21 22:16 ` Lars Marowsky-Bree
2005-04-21 21:31 goggin, edward
2005-04-21 21:49 ` Lars Marowsky-Bree
2005-04-21 21:02 goggin, edward
2005-04-19 17:19 Andreas Herrmann
2005-04-21 16:42 ` Patrick Mansfield
2005-04-21 19:54 ` Lars Marowsky-Bree
2005-04-21 22:13 ` Patrick Mansfield
2005-04-21 22:52 ` Lars Marowsky-Bree
2005-04-22 0:22 ` Patrick Mansfield
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=20050503111102.GJ1285@marowsky-bree.de \
--to=lmb@suse.de \
--cc=aherrman@de.ibm.com \
--cc=dm-devel@redhat.com \
--cc=linux-scsi@vger.kernel.org \
--cc=tpepper@gmail.com \
--cc=tranlan@us.ibm.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