public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockrwd@gmail.com>
To: Mike Hayward <hayward@loup.net>
Cc: linux-kernel@vger.kernel.org, mvds.00@gmail.com
Subject: Re: SCSI GENERIC command queueing for block storage is unstable.
Date: Mon, 15 Mar 2010 17:31:59 -0600	[thread overview]
Message-ID: <4B9EC36F.8010404@gmail.com> (raw)
In-Reply-To: <201003151825.o2FIPUTV006948@alien.loup.net>

On 03/15/2010 12:25 PM, Mike Hayward wrote:
> After discovering that O_NONBLOCK reads and writes were actually
> blocking calls, I attempted to use the SCSI generic driver for
> nonblocking io.  The good news is that it is nonblocking; the bad news
> is that it is not dependable in any of the systems I have tested with.
>
> Does anyone know if these defects have been fixed in later kernels?
>
> 1. When queueing, write can occassionally return errno 12 (ENOMEM, Cannot
>     allocate memory).  This is documented in the SCSI GENERIC HOWTO,
>     however only for indirect io and it says extremely rare.  I can cause
>     it easily within a few hours and it can return even for direct io when
>     no io's are queued and 80% of the ram is free or in buffer cache.  The
>     fd polls as available for writing, but retrying never clears the error
>     and the fd is no longer usable.  This is a complete show stopper.
>
>     Linux 2.6.22.1-32.fc6 #1 SMP Wed Aug 1 14:30:16 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux

First off, have you tested any of these problems against a newer kernel?

  reply	other threads:[~2010-03-15 23:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-15 18:25 SCSI GENERIC command queueing for block storage is unstable Mike Hayward
2010-03-15 23:31 ` Robert Hancock [this message]
2010-03-17  3:09   ` Mike Hayward
2010-03-17  3:30   ` Mike Hayward

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=4B9EC36F.8010404@gmail.com \
    --to=hancockrwd@gmail.com \
    --cc=hayward@loup.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mvds.00@gmail.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