From owner-freebsd-current@FreeBSD.ORG  Sun Dec 20 15:59:16 2009
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from hub.freebsd.org (localhost [127.0.0.1])
	by hub.freebsd.org (Postfix) with ESMTP id 8E5A410656A4;
	Sun, 20 Dec 2009 15:59:15 +0000 (UTC)
	(envelope-from nork@FreeBSD.org)
Date: Mon, 21 Dec 2009 00:59:09 +0900
From: Norikatsu Shigemura <nork@FreeBSD.org>
To: Alexander Motin <mav@freebsd.org>
Message-Id: <20091221005909.c719571a.nork@FreeBSD.org>
In-Reply-To: <4B262119.6090904@FreeBSD.org>
References: <1258575782.00184876.1258562404@10.7.7.3>
	<mailpost.1258563606.7337474.35089.mailing.freebsd.current@FreeBSD.cs.nctu.edu.tw>
	<1258579386.00184908.1258567802@10.7.7.3>
	<1258590193.00184983.1258579804@10.7.7.3>
	<4B262119.6090904@FreeBSD.org>
X-Mailer: Sylpheed 2.7.1 (GTK+ 2.18.4; i386-portbld-freebsd8.0)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: FreeBSD-Current <freebsd-current@freebsd.org>,
	Norikatsu Shigemura <nork@FreeBSD.org>, Ivan Voras <ivoras@freebsd.org>
Subject: Re: How do I use NCQ of Intel X25-E(SSD) on ahci(4)?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Dec 2009 15:59:16 -0000

Hi mav!

On Mon, 14 Dec 2009 13:27:21 +0200
Alexander Motin <mav@freebsd.org> wrote:
> >> while scheduling requests. I didn't do it yet, just because most of
> >> devices able to handle all 32 tags possible on SATA. This Intel SSD is
> >> one of rare exceptions.
> > Ok, (still thinking about something that could be MFC-able in an
> > emergency), how about adding a loader tunable integer instead of "32"?
> Just for note, it is already fixed and merged.

	Thank you!  Yes, I confirmed!

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0: <SSDSA2SH064G1GC INTEL 045C8790> ATA-7 SATA 2.x device
ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO size 8192bytes)
ada0: Command Queueing enabled
ada0: 61057MB (125045424 512 byte sectors: 16H 63S/T 16383C)
ada1 at ahcich1 bus 0 scbus1 target 0 lun 0
ada1: <WDC WD10EADS-00L5B1 01.01A01> ATA-8 SATA 2.x device
ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO size 8192bytes)
ada1: Command Queueing enabled
ada1: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# camcontrol tags ada0
(pass0:ahcich0:0:0:0): device openings: 31
# camcontrol tags ada1
(pass1:ahcich1:0:0:0): device openings: 32
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -