From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756922AbcHWGV2 (ORCPT ); Tue, 23 Aug 2016 02:21:28 -0400 Received: from mx0b-00003501.pphosted.com ([67.231.152.68]:59206 "EHLO mx0a-000cda01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1756884AbcHWGVV (ORCPT ); Tue, 23 Aug 2016 02:21:21 -0400 Authentication-Results: seagate.com; dkim=pass header.s="google" header.d=seagate.com MIME-Version: 1.0 In-Reply-To: References: <20160822042321.24367-1-shaun@tancheff.com> <20160822042321.24367-2-shaun@tancheff.com> From: Shaun Tancheff Date: Tue, 23 Aug 2016 01:20:28 -0500 Message-ID: Subject: Re: [PATCH v6 1/4] libata: Safely overwrite attached page in WRITE SAME xlat To: Tom Yan Cc: Shaun Tancheff , linux-ide@vger.kernel.org, LKML , Tejun Heo , Christoph Hellwig , "Martin K . Petersen" , Damien Le Moal , Hannes Reinecke , Josh Bingaman , Hannes Reinecke Content-Type: text/plain; charset=UTF-8 X-Proofpoint-PolicyRoute: Outbound X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2016-08-23_03:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 suspectscore=1 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 impostorscore=0 lowpriorityscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1604210000 definitions=main-1608230065 X-Proofpoint-Spam-Policy: Default Domain Policy Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 23, 2016 at 12:26 AM, Tom Yan wrote: > It is always 1 merely because we prefer sticking to that. Say we want > to enable multi-block payload now, it won't be 1 anymore. Sorry, I though that DSM TRIM is using 512 bytes here because WRITE_SAME_16 has a payload of a single logical sector. > Also note that the payload is NOT always fully-filled. Oh, I was considering filling the remainder of the buffer with 0's using memset() as you described to be "filly-filled" in this case. Sorry for the confusion. -- Shaun Tancheff