From: jthumshirn@suse.de (Johannes Thumshirn)
Subject: remove long broken SCSI to NVMe translations
Date: Thu, 22 Jun 2017 21:21:05 +0200 [thread overview]
Message-ID: <20170622192105.GC4445@linux-x5ow.site> (raw)
In-Reply-To: <922f6c05-cb61-9973-2c2c-823f31b5d082@hpe.com>
On Thu, Jun 22, 2017@12:31:55PM -0600, Micah Parrish wrote:
> From HPE's perspective, we don't want NVME-SCSI translation removed from
> Linux. We do drive firmware updates and other management functions using a
> common cross platform management API which works on VMWare, Windows and
> Linux, and it relies on SCSI on all 3. This software (called SOULAPI) is
> common across most of our drives and enclosures, so putting in a special
> case for nvme on linux would be difficult. In the short term we'd have to
> wrap nvme-cli, which would introduce a new dependency. Long term maybe we
> could rewrite our API to use native NVME commands on all supported OSes.
>
> The reason the scsi translation has been broken so long is that we don't
> test firmware updates with upstream kernels. From our perspective it broke
> in the last enterprise update cycle, but we didn't discover it because we
> didn't have a firmware update for these drives. There are some process
> improvements we could make there to catch this kind of bug sooner, and I
> will be discussing them internally.
There's no need to wrap nvme-cli, the firmware download litterally is the
following:
int nvme_download_firmware(int fd, uint32_t offset, uint32_t len, void *data,
uint32_t slot)
{
struct nvme_admin_cmd cmd = {
.opcode = nvme_admin_download_fw,
.addr = (uint64_t)data,
.data_len = len,
.cdw10 = (len >> 2) - 1,
.cdw11 = offset >> 2,
};
ioctl(fd, NVME_IOCTL_ADMIN_CMD, &cmd);
struct nvme_admin_cmd cmd = {
.opcode = nvme_admin_activate_fw,
.cd10 = (action << 3) | slot;
};
ioctl(fd, NVME_IOCTL_ADMIN_CMD, &cmd);
}
--
Johannes Thumshirn Storage
jthumshirn at suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg
GF: Felix Imend?rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N?rnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
next prev parent reply other threads:[~2017-06-22 19:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 6:35 remove long broken SCSI to NVMe translations Christoph Hellwig
2017-06-14 6:35 ` [PATCH 1/2] nvme-scsi: remove TEST UNIT READY emuation Christoph Hellwig
2017-06-14 6:35 ` [PATCH 2/2] nvme-scsi: remove FORMAT UNIT and WRITE BUFFER emulations Christoph Hellwig
2017-06-14 15:00 ` remove long broken SCSI to NVMe translations Keith Busch
2017-06-14 15:01 ` Christoph Hellwig
2017-06-16 6:11 ` Hannes Reinecke
2017-06-16 8:31 ` Christoph Hellwig
2017-06-16 13:57 ` Linda Knippers
2017-06-20 6:48 ` Christoph Hellwig
2017-06-20 14:27 ` Keith Busch
2017-06-22 18:31 ` Micah Parrish
2017-06-22 19:21 ` Johannes Thumshirn [this message]
2017-06-30 13:07 ` Judy Brock
2017-06-14 15:14 ` 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=20170622192105.GC4445@linux-x5ow.site \
--to=jthumshirn@suse.de \
/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