From owner-freebsd-hardware@FreeBSD.ORG Sat Sep 14 08:15:00 2013 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 01E72803 for ; Sat, 14 Sep 2013 08:15:00 +0000 (UTC) (envelope-from rp_freebsd@mac.com) Received: from st11p00mm-asmtp004.mac.com (st11p00mm-asmtpout004.mac.com [17.172.81.3]) by mx1.freebsd.org (Postfix) with ESMTP id CEA65286D for ; Sat, 14 Sep 2013 08:14:59 +0000 (UTC) Received: from [192.168.1.3] (c-98-207-91-59.hsd1.ca.comcast.net [98.207.91.59]) by st11p00mm-asmtp004.mac.com (Oracle Communications Messaging Server 7u4-27.08(7.0.4.27.7) 64bit (built Aug 22 2013)) with ESMTPSA id <0MT3001V6TGOVF70@st11p00mm-asmtp004.mac.com> for freebsd-hardware@freebsd.org; Sat, 14 Sep 2013 07:14:53 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794,1.0.431,0.0.0000 definitions=2013-09-13_10:2013-09-13,2013-09-13,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1308280000 definitions=main-1309140001 User-Agent: Microsoft-MacOutlook/14.3.7.130812 Date: Sat, 14 Sep 2013 00:14:47 -0700 Subject: What's the state of AF-4Kn support? From: Ravi Pokala To: "freebsd-hardware@freebsd.org" Message-id: Thread-topic: What's the state of AF-4Kn support? MIME-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Sep 2013 08:15:00 -0000 Hi folks, AF-4Kn drives (4096-byte blocks, logical as well as physical) have been on the HDD vendors' enterprise roadmaps for years and years, but now we're starting to get samples, so it's time to start testing. :-S What does 4Kn support look like in -HEAD? I know UFS's defaults (32KB blocks / 4KB fragments) are 4Kn-friendly, and that `gpart' handles alignment properly. What about direct drive I/O (i.e. do the device drivers do the proper read/modify/write stuff if you try to write a partial block)? What about the bootstrap code; I've looked at pmbr.s and gptboot.c, and it's not clear if they DTRT in the face of 4Kn drives. Also, what about 9-STABLE? (My apologies if this is all documented somewhere; I looked around for a bit, but couldn't find it, so a pointer to TFM for me to R would be great.) Thanks! --rp