public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>,
	Alan Cox <alan@redhat.com>, Douglas Gilbert <dougg@torque.net>,
	Arjan van de Ven <arjanv@redhat.com>
Subject: Re: sg driver and Fedora Core 2
Date: Sun, 30 May 2004 12:20:42 +0200	[thread overview]
Message-ID: <20040530102041.GF18613@suse.de> (raw)
In-Reply-To: <40B8CF34.6080901@pobox.com>

On Sat, May 29 2004, Jeff Garzik wrote:
> James Bottomley wrote:
> >On Sat, 2004-05-29 at 12:27, Jeff Garzik wrote:
> >
> >>Really what needs to happen is a generic userland tap attaches to a 
> >>chrdev, issues an ioctl(2) to attach to a request_queue, and then does 
> >>read(2)/write(2)/mmap(2) to communicate with the request_queue.
> >>
> >>:)
> >>
> >>Call it /dev/bsg, or somesuch.
> >
> >
> >Well, this touches on something else I'm thinking about: lazy
> >attachment.  In multi thousand disc environments, you don't want us
> >wasting resources allocating a queue and reading a partition table for
> >all of them; you really only want to do that for the devices you're
> >actually going to use.  Once we have this, I think dual attachment will
> >be a dead issue.
> 
> 
> Regardless of lazy attachment, request_queues need to support multiple 
> simultaneous producers of struct request's.

That has always been the case, even if it was just driver private use
before. As such there is no dual-attachment issue for sg.

-- 
Jens Axboe


  reply	other threads:[~2004-05-30 10:23 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-28 14:05 sg driver and Fedora Core 2 Douglas Gilbert
2004-05-28 14:18 ` Jens Axboe
2004-05-28 14:28   ` Jens Axboe
2004-05-28 17:25 ` Alan Cox
2004-05-29 15:55   ` James Bottomley
2004-05-29 15:57     ` Alan Cox
2004-05-29 16:07       ` James Bottomley
2004-05-29 16:29         ` Alan Cox
2004-05-29 16:36           ` Arjan van de Ven
2004-05-29 16:42             ` Alan Cox
2004-05-29 17:45               ` Matthew Wilcox
2004-05-29 16:49           ` James Bottomley
2004-05-29 16:56             ` Alan Cox
2004-05-29 17:28               ` James Bottomley
2004-05-29 17:38                 ` Alan Cox
2004-05-29 17:27             ` Jeff Garzik
2004-05-29 17:29               ` Jens Axboe
2004-05-30 10:37                 ` Douglas Gilbert
2004-05-30 10:41                   ` Alan Cox
2004-06-07  8:56                     ` Douglas Gilbert
2004-05-29 17:35               ` Alan Cox
2004-05-29 17:42                 ` Jeff Garzik
2004-05-29 17:38               ` James Bottomley
2004-05-29 17:46                 ` Alan Cox
2004-05-29 17:58                 ` Jeff Garzik
2004-05-30 10:20                   ` Jens Axboe [this message]
2004-05-29 16:24       ` Arjan van de Ven
2004-05-28 17:39 ` Arjan van de Ven

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=20040530102041.GF18613@suse.de \
    --to=axboe@suse.de \
    --cc=James.Bottomley@steeleye.com \
    --cc=alan@redhat.com \
    --cc=arjanv@redhat.com \
    --cc=dougg@torque.net \
    --cc=jgarzik@pobox.com \
    --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