public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bsg, block layer sg
Date: Thu, 02 Mar 2006 06:22:48 -0500	[thread overview]
Message-ID: <4406D588.5040900@pobox.com> (raw)
In-Reply-To: <20060302111945.GG4329@suse.de>

Jens Axboe wrote:
> Hi,
> 
> After all that SG_IO and cdrecord talk, I decided to brush off the bsg
> driver I wrote some time ago. Basically this is a full (aims to be at
> least, probably still some minor bits missing) SG v3 interface. It
> supports both SG_IO (which we just pass through for now), as well as
> read/write and readv/writev of sg_io_hdr structures.
> 
> What's new in this area is that the bsg character device is closely tied
> to the block device. This relationsship is depicted in sysfs. bsg
> devices will show up in /sys/class/bsg/<devname>, and there is a link
> from /sys/block/<devname>/queue/bsg to that directory. With some
> udev/hotplug magic, it should create device nodes for you automatically.
> 
> TODO:
> 
> - Fold block/scsi_ioctl.c and block/bsg.c into one
> - Further improve the sysfs relations between a device and bsg
> - Test and so on
> 
> Probably some bugs still pending, it works for me though.

For my part, this gets a strong ACK.  I've been waiting for something 
like this since an OLS discussion years ago.

Thanks Jens!

	Jeff




  reply	other threads:[~2006-03-02 11:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-02 11:19 [PATCH] bsg, block layer sg Jens Axboe
2006-03-02 11:22 ` Jeff Garzik [this message]
2006-03-05  2:08 ` Andrew Morton
2006-03-06  8:57   ` Jens Axboe
2006-03-06  9:13     ` Andrew Morton
2006-03-06  9:19       ` Jens Axboe
2006-03-06  9:25         ` Jens Axboe
2006-03-06 18:30 ` Erik Andersen
2006-03-06 18:57   ` Jens Axboe

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=4406D588.5040900@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=axboe@suse.de \
    --cc=linux-kernel@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