mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	linux-scsi@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: TRIM/UNMAP/DISCARD via ATA Passthrough
Date: Thu, 15 Sep 2016 12:07:20 -0400	[thread overview]
Message-ID: <yq1twdhb0zr.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <CAHmME9pX1sSdFLfsgBqunh=5ttmPg5-vAzvTEfD1Xt4NBk6JzA@mail.gmail.com> (Jason A. Donenfeld's message of "Thu, 15 Sep 2016 17:41:25 +0200")

>>>>> "Jason" == Jason A Donenfeld <Jason@zx2c4.com> writes:

Jason,

>> How do they signal that they support the passthrough?

Jason> Through the usual SCSI ATA-passthrough interface, "SAT" (SCSI-ATA
Jason> Command Translation) -- ATA PASS THROUGH SCSI (16) and ATA PASS
Jason> THROUGH SCSI (12).

But how do they signal that ATA passthrough is possible? Is there an ATA
Information VPD page? Is REPORT SUPPORTED OPERATION CODES supported?

We need really solid discovery data before we can entertain enabling
something like this.

-- 
Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2016-09-15 16:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-12 18:50 Jason A. Donenfeld
2016-09-13 17:45 ` Henrique de Moraes Holschuh
2016-09-14 18:37 ` Martin K. Petersen
2016-09-15 15:41   ` Jason A. Donenfeld
2016-09-15 16:07     ` Martin K. Petersen [this message]
2016-09-15 20:52       ` Jason A. Donenfeld
2016-09-16 11:16         ` Hannes Reinecke
2016-09-16 15:53           ` Austin S. Hemmelgarn
2016-09-16 16:21             ` James Bottomley
2016-09-16 17:06               ` Austin S. Hemmelgarn
2016-09-17  1:24                 ` Jason A. Donenfeld
2016-09-17  5:14                 ` James Bottomley
2016-09-19 13:01                   ` Austin S. Hemmelgarn

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=yq1twdhb0zr.fsf@sermon.lab.mkp.net \
    --to=martin.petersen@oracle.com \
    --cc=Jason@zx2c4.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®