From: Christoph Hellwig <hch@infradead.org>
To: Boaz Harrosh <ooo@electrozaur.com>
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 06:01:18 -0700 [thread overview]
Message-ID: <20141021130118.GA6122@infradead.org> (raw)
In-Reply-To: <544655E8.8070004@electrozaur.com>
On Tue, Oct 21, 2014 at 03:47:36PM +0300, Boaz Harrosh wrote:
> It is used in testing, its a good way to compare ext4 over objects
> vs exofs over objects, kind of compare apples with apples.
> (Also at the get go it was a good test that found some bugs in the
> bring up of the osd target)
>
> If there is an old tagging API need removing its fine to just drop
> the support, and/or do the minimal change possible. What was the
> tag used for anyway?
>
> If it bothers you very much then please remove it, send a patch
> and I'll ACK it.
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.
> [Just that I thought we don't do that. I can show you a dozen
> ISA scsi LLD controllers which are a complete pain in the neck
> with a all subsection core support. There is not a single system
> on the planet that has this even possible, yet we do not remove
> them nor the ISA bus crap. osdblk at least is a SW only exercise
> that can be very much valid in any system.
> ]
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.
next prev parent reply other threads:[~2014-10-21 13:01 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 [this message]
2014-10-21 13:24 ` Boaz Harrosh
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=20141021130118.GA6122@infradead.org \
--to=hch@infradead.org \
--cc=jgarzik@pobox.com \
--cc=jgpobox@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ooo@electrozaur.com \
--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 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.