From: Boaz Harrosh <ooo@electrozaur.com>
To: Christoph Hellwig <hch@lst.de>,
axboe@kernel.dk, martin.petersen@oracle.com
Cc: Johannes Thumshirn <jthumshirn@suse.de>,
Benjamin Block <bblock@linux.vnet.ibm.com>,
linux-scsi@vger.kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: remove exofs, the T10 OSD code and block/scsi bidi support V4
Date: Mon, 4 Feb 2019 22:31:39 +0200 [thread overview]
Message-ID: <3be11773-5ea9-4c08-25a5-dc556ded2d6f@electrozaur.com> (raw)
In-Reply-To: <20190201075557.9249-1-hch@lst.de>
On 01/02/19 09:55, Christoph Hellwig wrote:
> The only real user of the T10 OSD protocol, the pNFS object layout
> driver never went to the point of having shipping products, and we
> removed it 1.5 years ago. Exofs is just a simple example without
> real life users.
>
> The code has been mostly unmaintained for years and is getting in the
> way of block / SCSI changes,
For the 4th time: Which ?
> and does not even work properly currently,
> so I think it's finally time to drop it.
>
> Quote from Boaz:
>
Hello? anyone home?
Please resend without the below Quote!!!
Because yes I said that but I have also said the opposite. And I have clearly
stated in reaction to the last 3 resends. That I now oppose to the below statement.
And that you should please remove it.
Do your own text please. Don't drag me in the mud
> "As I said then. It is used in Universities for studies and experiments.
> Every once in a while. I get an email with questions and reports.
>
> But yes feel free to remove the all thing!!
>
> I guess I can put it up on github. In a public tree.
>
> Just that I will need to forward port it myself, til now you guys
> been doing this for me ;-)"
>
> Now the last time this caused a bit of a stir, but still no actual users,
> not even for SG_IO passthrough commands. So here we go again, this time
> including removing everything in the scsi and block layer supporting it,
> and thus shrinking struct request.
>
NAK-by: Boaz harrosh <ooo@electrozaur.com>
For what ever that means ...
Cheers
Boaz
next prev parent reply other threads:[~2019-02-04 20:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 7:55 remove exofs, the T10 OSD code and block/scsi bidi support V4 Christoph Hellwig
2019-02-01 7:55 ` [PATCH 1/8] bsg: refactor bsg_ioctl Christoph Hellwig
2019-02-01 7:55 ` [PATCH 2/8] bsg-lib: handle bidi requests without block layer help Christoph Hellwig
2019-02-01 7:55 ` [PATCH 3/8] fs: remove exofs Christoph Hellwig
2019-02-01 7:55 ` [PATCH 4/8] scsi: remove the SCSI OSD library Christoph Hellwig
2019-02-01 7:55 ` [PATCH 5/8] scsi: remove bidirectional command support Christoph Hellwig
2019-02-01 7:55 ` [PATCH 6/8] scsi: stop setting up request->special Christoph Hellwig
2019-02-01 7:55 ` [PATCH 7/8] block: remove req->special Christoph Hellwig
2019-02-04 8:01 ` Christoph Hellwig
2019-02-01 7:55 ` [PATCH 8/8] block: remove bidi support Christoph Hellwig
2019-02-01 15:13 ` remove exofs, the T10 OSD code and block/scsi bidi support V4 Jens Axboe
2019-02-04 20:31 ` Boaz Harrosh [this message]
2019-02-05 17:16 ` Christoph Hellwig
2019-02-05 3:47 ` Martin K. Petersen
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=3be11773-5ea9-4c08-25a5-dc556ded2d6f@electrozaur.com \
--to=ooo@electrozaur.com \
--cc=axboe@kernel.dk \
--cc=bblock@linux.vnet.ibm.com \
--cc=hch@lst.de \
--cc=jthumshirn@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
/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;
as well as URLs for NNTP newsgroup(s).