mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: TRIM/UNMAP/DISCARD via ATA Passthrough
Date: Fri, 16 Sep 2016 13:16:35 +0200	[thread overview]
Message-ID: <5af202ea-a632-28c2-515f-c361e27de5da@suse.de> (raw)
In-Reply-To: <CAHmME9qq5vSC+hZckCystU6cdRPihO492U2B2-pozbwg=3_5nw@mail.gmail.com>

On 09/15/2016 10:52 PM, Jason A. Donenfeld wrote:
> Hi Martin,
> 
> On Thu, Sep 15, 2016 at 6:07 PM, Martin K. Petersen
>> 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.
> 
> `sg_opcodes` said invalid request, so I think there isn't REPORT
> SUPPORTED OPERATION CODES, and `sg_vpd -p ai` came up illegal too.
> 
> However, sg_sat_identify worked reliably, which means a solid way of
> probing this would be to send IDENTIFY DEVICE ATA via SG_ATA_16 or
> SG_ATA_12.
> 
> Let me know and I can give you access to the hardware if you're curious.
> 
Sadly, that's not sufficient.
linux is not the only provider of an SATL (mpt3sas being the most
prominent other one).
And while they might support ATA_12/ATA_16, there is no indication that
you can pass DSM TRIM that way.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)

  reply	other threads:[~2016-09-16 11:16 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
2016-09-15 20:52       ` Jason A. Donenfeld
2016-09-16 11:16         ` Hannes Reinecke [this message]
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=5af202ea-a632-28c2-515f-c361e27de5da@suse.de \
    --to=hare@suse.de \
    --cc=Jason@zx2c4.com \
    --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

all inboxes | Powered by JetHome®