All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: James Smart <james.smart@emulex.com>,
	linux-scsi@vger.kernel.org,
	"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH 15/21] lpfc: Implement support for wire-only DIF devices
Date: Tue, 07 Apr 2015 19:13:03 -0400	[thread overview]
Message-ID: <yq16197ilc0.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <20150405160613.GA8622@infradead.org> (Christoph Hellwig's message of "Sun, 5 Apr 2015 09:06:13 -0700")

>>>>> "Christoph" == Christoph Hellwig <hch@infradead.org> writes:

>> This patch adds the ability to support auto-enablement of wire-only
>> DIF (DIF is generated on TX to target, stripped on RX; OS unaware DIF
>> in use) for a select set of devices. Currently, there is only 1
>> device vendor supported: 3PARdata. When the feature is enabled,
>> Inquiry commands are trapped, the vendor matched, and DIF enablement
>> checked. In 3Par's case, there's a vendor specific check to see if
>> the LUN supports DIF.  If supported, DIF will be enabled on a per-lun
>> basis.  The driver will trap READS/WRITEs from the OS, check for LUN
>> DIF enablement, and if set, turns on write-only DIF.

Christoph> NAK. We do support proper DIF, and anyone who wants it should
Christoph> enable the real thing.

Christoph> And even if we would want to support a hack like this we'd do
Christoph> it genericly an not in a driver.

Agree completely.

-- 
Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2015-04-07 23:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-03 21:13 [PATCH 15/21] lpfc: Implement support for wire-only DIF devices James Smart
2015-04-05 11:12 ` Sebastian Herbszt
2015-04-05 16:06 ` Christoph Hellwig
2015-04-07 23:13   ` Martin K. Petersen [this message]
2015-04-09 20:58   ` James Smart
2015-04-09 21:20     ` Martin K. Petersen
  -- strict thread matches above, loose matches on Subject: below --
2015-02-05 19:25 James Smart

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=yq16197ilc0.fsf@sermon.lab.mkp.net \
    --to=martin.petersen@oracle.com \
    --cc=hch@infradead.org \
    --cc=james.smart@emulex.com \
    --cc=linux-scsi@vger.kernel.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.