From: Jeff Garzik <jgarzik@pobox.com>
To: SCSI Mailing List <linux-scsi@vger.kernel.org>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
Alan Cox <alan@redhat.com>, Douglas Gilbert <dougg@torque.net>,
Arjan van de Ven <arjanv@redhat.com>, Jens Axboe <axboe@suse.de>
Subject: Re: sg driver and Fedora Core 2
Date: Sat, 29 May 2004 13:27:58 -0400 [thread overview]
Message-ID: <40B8C81E.3050106@pobox.com> (raw)
In-Reply-To: <1085849399.2004.101.camel@mulgrave>
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.
The SG_IO ioctl won't work for all cases, since some block devices may
rightly wish to limit (or block) multiple openers on the blkdev itself.
OTOH, the SG_IO ioctl does eliminate the userland app needing to
worry about _any_ target/addressing information, since that is implicit
in the dentry pointing to the blkdev's inode.
Jeff
next prev parent reply other threads:[~2004-05-29 17:28 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 [this message]
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
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=40B8C81E.3050106@pobox.com \
--to=jgarzik@pobox.com \
--cc=James.Bottomley@steeleye.com \
--cc=alan@redhat.com \
--cc=arjanv@redhat.com \
--cc=axboe@suse.de \
--cc=dougg@torque.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.