All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "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: Thu, 15 Sep 2016 22:52:34 +0200	[thread overview]
Message-ID: <CAHmME9qq5vSC+hZckCystU6cdRPihO492U2B2-pozbwg=3_5nw@mail.gmail.com> (raw)
In-Reply-To: <yq1twdhb0zr.fsf@sermon.lab.mkp.net>

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.

Regards,
Jason

  reply	other threads:[~2016-09-15 20:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-12 18:50 TRIM/UNMAP/DISCARD via ATA Passthrough 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 [this message]
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='CAHmME9qq5vSC+hZckCystU6cdRPihO492U2B2-pozbwg=3_5nw@mail.gmail.com' \
    --to=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 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.