From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Christoph Hellwig <hch@lst.de>
Cc: ooo@electrozaur.com, martin.petersen@oracle.com,
trond.myklebust@primarydata.com, axboe@kernel.dk,
osd-dev@open-osd.org, linux-nfs@vger.kernel.org,
linux-scsi@vger.kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: RFC: drop the T10 OSD code and its users
Date: Thu, 13 Apr 2017 22:27:38 -0400 [thread overview]
Message-ID: <yq1inm7wwo5.fsf@oracle.com> (raw)
In-Reply-To: <20170412160109.10598-1-hch@lst.de> (Christoph Hellwig's message of "Wed, 12 Apr 2017 18:01:05 +0200")
Christoph,
> The only real user of the T10 OSD protocol, the pNFS object layout
> driver never went to the point of having shipping products, and the
> other two users (osdblk and exofs) were simple example of it's usage.
>
> The code has been mostly unmaintained for years and is getting in the
> way of block / SCSI changes, so I think it's finally time to drop it.
No particular objections from me.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2017-04-14 2:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 16:01 RFC: drop the T10 OSD code and its users Christoph Hellwig
2017-04-12 16:01 ` [PATCH 1/4] block: remove the osdblk driver Christoph Hellwig
2017-04-19 7:21 ` Boaz Harrosh
2017-04-12 16:01 ` [PATCH 2/4] fs: remove exofs Christoph Hellwig
2017-04-12 16:01 ` [PATCH 3/4] nfs: remove the objlayout driver Christoph Hellwig
2017-04-20 20:18 ` Trond Myklebust
2017-04-21 10:51 ` Christoph Hellwig
2017-04-21 13:17 ` Boaz Harrosh
[not found] ` <B6CCD2A9-4691-45DC-AD60-E9A2ECDE22D3@primarydata.com>
2017-04-23 9:36 ` Boaz Harrosh
2017-04-21 7:27 ` Valentin Rothberg
2017-04-21 10:50 ` Christoph Hellwig
2017-04-12 16:01 ` [PATCH 4/4] scsi: remove the SCSI OSD library Christoph Hellwig
2017-04-14 2:27 ` Martin K. Petersen [this message]
2017-04-18 16:24 ` RFC: drop the T10 OSD code and its users Boaz Harrosh
2017-04-18 17:06 ` Chandy, John
2017-04-19 15:11 ` 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=yq1inm7wwo5.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=ooo@electrozaur.com \
--cc=osd-dev@open-osd.org \
--cc=trond.myklebust@primarydata.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