From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tejun Heo Subject: Re: [PATCHv2 05/14] libata: NCQ Encapsulation for READ LOG DMA EXT Date: Wed, 13 Apr 2016 14:07:35 -0400 Message-ID: <20160413180735.GD3676@htj.duckdns.org> References: <1460443678-57934-1-git-send-email-hare@suse.de> <1460443678-57934-6-git-send-email-hare@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mail-yw0-f193.google.com ([209.85.161.193]:36693 "EHLO mail-yw0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751211AbcDMSHi (ORCPT ); Wed, 13 Apr 2016 14:07:38 -0400 Content-Disposition: inline In-Reply-To: <1460443678-57934-6-git-send-email-hare@suse.de> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Hannes Reinecke Cc: linux-ide@vger.kernel.org, "Martin K. Petersen" , Christoph Hellwig , James Bottomley , Shaun Tancheff , Damien Le Moal , linux-scsi@vger.kernel.org, Hannes Reinecke On Tue, Apr 12, 2016 at 08:47:49AM +0200, Hannes Reinecke wrote: > Recent devices can use NCQ encapsulation for READ LOG DMA EXT, > so we should be using it if available. Does this have any actual benefits than being new and shiny? It's being called from EH path where we know that no other commands are in flight. Thanks. -- tejun