From: Christoph Hellwig <hch@infradead.org>
To: Shaun Tancheff <shaun@tancheff.com>
Cc: linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org,
"James E . J . Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
Tejun Heo <tj@kernel.org>,
Shaun Tancheff <shaun.tancheff@seagate.com>
Subject: Re: [PATCH v2] Add support for SCT Write Same
Date: Thu, 9 Jun 2016 02:22:12 -0700 [thread overview]
Message-ID: <20160609092212.GA7459@infradead.org> (raw)
In-Reply-To: <1465453967-11085-2-git-send-email-shaun@tancheff.com>
> + if (ata_id_sct_write_same(dev->id))
> + sdev->sct_write_same = 1;
> +
What's the point of this flag? It should simply clear the no_write_same
flag for this device. Due to the way how we have both a per-host and
per-device flag that might not be completely trivial, but untangling
that mess might be a good idea anyway.
> @@ -3305,6 +3308,37 @@ static unsigned int ata_scsi_write_same_xlat(struct ata_queued_cmd *qc)
> goto invalid_param_len;
>
> buf = page_address(sg_page(scsi_sglist(scmd)));
> +
> + if (ata_id_sct_write_same(dev->id)) {
Various comments:
- The plain page_address above looks harmful, how do we know that
the page is mapped into kernel memory? This might actually be broken
already, though.
- Why is this below the check that rejects non-unmap WRITE SAME
commands?
- Shouldn't we still translate discard command to TRIM? Maybe we
need a check of the operation in the request structure..
next prev parent reply other threads:[~2016-06-09 9:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 6:32 [PATCH v2] Add support for Write Same via SCT Shaun Tancheff
2016-06-09 6:32 ` [PATCH v2] Add support for SCT Write Same Shaun Tancheff
2016-06-09 9:22 ` Christoph Hellwig [this message]
2016-06-10 3:24 ` Shaun Tancheff
2016-06-13 8:02 ` Christoph Hellwig
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=20160609092212.GA7459@infradead.org \
--to=hch@infradead.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=shaun.tancheff@seagate.com \
--cc=shaun@tancheff.com \
--cc=tj@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;
as well as URLs for NNTP newsgroup(s).