public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <ooo@electrozaur.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Jeff Garzik <jgpobox@gmail.com>, Jeff Garzik <jgarzik@pobox.com>,
	Kernel development list <linux-kernel@vger.kernel.org>,
	osd-dev@open-osd.org
Subject: Re: state of the osdblk driver?
Date: Tue, 21 Oct 2014 16:24:28 +0300	[thread overview]
Message-ID: <54465E8C.6030302@electrozaur.com> (raw)
In-Reply-To: <20141021130118.GA6122@infradead.org>

On 10/21/2014 04:01 PM, Christoph Hellwig wrote:
<>
> 
> I'm mostly just trying to figure out if anyone cares.  Would you be
> willing to sign up as a maintainer, and maybe even look into a blk-mq
> conversion?  I'd be happy to help to answer questions and review it.
> 

I thought I was kind of am ;-) .

Good point I will put it on my list of things to do. Meanwhile can
I help you with the immediate problem of the tagging? could you do
something most brutal that even removes the tag support, just to
get you going?

And speaking of osdblk. Should it be its own full blown driver
or should it be under dm ? I know that at some LSF people said
it is better placed there? Specially since for a long time I wanted
to base it over ORE and not directly libosd so to support
RAID0/1/5/6 under the one simple block device.

> 
> Not sure what exactly you mean, but I'm open to any serious proposal to
> get rid of not actually usable cruft in old SCSI HBA drivers.  Feel
> free to send a proposal to linux-scsi - I was planning to come up with
> one of my own, but never got to it.
> 

Yes exactly that!
I wish I could have the time, perhaps one day I will. There is so much
more cleaning I can see.

Thanks Christoph
Boaz


      reply	other threads:[~2014-10-21 13:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-21 12:06 state of the osdblk driver? Christoph Hellwig
2014-10-21 12:21 ` Jeff Garzik
2014-10-21 12:47   ` Boaz Harrosh
2014-10-21 12:56     ` Jeff Garzik
2014-10-21 13:01     ` Christoph Hellwig
2014-10-21 13:24       ` Boaz Harrosh [this message]

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=54465E8C.6030302@electrozaur.com \
    --to=ooo@electrozaur.com \
    --cc=hch@infradead.org \
    --cc=jgarzik@pobox.com \
    --cc=jgpobox@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=osd-dev@open-osd.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