From owner-freebsd-hardware@FreeBSD.ORG Mon Sep 23 08:14:14 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 1DDED85B; Mon, 23 Sep 2013 08:14:14 +0000 (UTC) (envelope-from rozhuk.im@gmail.com) Received: from mail-bk0-x229.google.com (mail-bk0-x229.google.com [IPv6:2a00:1450:4008:c01::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7C4492705; Mon, 23 Sep 2013 08:14:13 +0000 (UTC) Received: by mail-bk0-f41.google.com with SMTP id na10so1099680bkb.28 for ; Mon, 23 Sep 2013 01:14:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=reply-to:from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:thread-index :content-language; bh=I4+ffUWY/nGbeiGVQmmRbHthV8hYdpRPz82yS4UcMO8=; b=cIj8bErT1fh9B4HxJseLOA9fssruqGszaP4n+pSWEWiRRYUQXvhChqBmE6BmbGVqGs LasI3HrjRWq4NK3D9Avk45uO65pt500RlxZYjnxzLkdm8aYvOtM1Q0ggExeOfrxBZ0wA Q3R95GElxr1TQkU8Z4O0GG0s6s6U2I5lKvzNwHDaQCZ4R7jcja6n52ecsMxc0YTIo+bQ zcB0UUCJyU6BtAL0tqv0KGlg2kJ0pZal+InyxNJqScrVer1qg2aSXZP+KAG94M0SLHcs 7Wn2qP9V05R4RdcVEFTk9UeAQfuGQOYyn8T34q5DSMmlKGjj1wc0oZoSquIMpd3ddHLq 7GHQ== X-Received: by 10.205.15.72 with SMTP id pt8mr16452362bkb.17.1379924051312; Mon, 23 Sep 2013 01:14:11 -0700 (PDT) Received: from rimwks1w7x64 ([2001:470:1f15:8e:c8ff:267:ab31:49e1]) by mx.google.com with ESMTPSA id jt14sm8176913bkb.0.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 23 Sep 2013 01:14:10 -0700 (PDT) From: rozhuk.im@gmail.com To: "'Jia-Shiun Li'" , "'Ravi Pokala'" References: In-Reply-To: Subject: RE: What's the state of AF-4Kn support? Date: Mon, 23 Sep 2013 12:13:58 +0400 Message-ID: <523ff852.4ee8cc0a.44b6.ffffacba@mx.google.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac64JWd+qAS+eZxGTWGEQro0C6z95AADz35Q Content-Language: ru Cc: freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Rozhuk.IM@gmail.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Sep 2013 08:14:14 -0000 # install gpart create -s GPT ada1 gpart show gpart add -i 1 -t freebsd-boot -b 40 -s 512 ada1 gpart add -i 2 -t freebsd-ufs -b 552 -s ..... ada1 gpart bootcode -b /boot/pmbr ada1 gpart bootcode -p /boot/gptboot -i 1 ada1 # for data gpart create -s GPT ada1 gpart show gpart add -i 1 -t freebsd-ufs -b 40 -s ..... ada1 > -----Original Message----- > From: owner-freebsd-hackers@freebsd.org [mailto:owner-freebsd- > hackers@freebsd.org] On Behalf Of Jia-Shiun Li > Sent: Monday, September 23, 2013 10:23 AM > To: Ravi Pokala > Cc: freebsd-hackers@freebsd.org; freebsd-hardware@freebsd.org > Subject: Re: What's the state of AF-4Kn support? > > On Wed, Sep 18, 2013 at 10:49 PM, Ravi Pokala > wrote: > > > > What you describe is the 'AF-512e' format - 4KB physical sectors > > *emulating* 512B logical sectors. See [ > > https://en.wikipedia.org/wiki/Advanced_Format#Advanced_Format_512e ; > > http://www.idema.org/?page_id=2153 ]. With AF-512e, yes, the HDD > > firmware does the read/modify/write for I/Os smaller than the > physical sector size. > > It is intended to be a low-cost/transitional format, allowing the HDD > > vendors to get the advantages of 4KB physical sectors (better error > > detection/correction algorithms, better areal density => lower cost) > > w/o breaking compatibility with decades of firmware and software that > > expect 512B logical sectors. > > > > What I'm asking about is AF-4kn - 4KB *logical* as well as physical > > sectors. All the enterprise HDD vendors have told us is that AF-4Kn > > drives expect data IO to be 4KB, and will reject smaller transfers. > > (*metadata* IO - SMART, IDENTIFY_DEVICE, READ_LOG/WRITE_LOG, etc - > > will remain 512B.) > > > > Doing some more digging, I found this post from ivoras which I missed > > the first time around [ > > http://ivoras.net/blog/tree/2011-01-01.freebsd-on-4k-sector- > drives.htm > > l ]; that tends to support my initial assessment - filesystem stuff > > should Just Work[tm] - plus adds the detail that direct drive I/O > (the > > example he gives is trying to `dd' 10 bytes) will be rejected because > > it is smaller than the raw-device access granularity. I've also > looked > > at 'ata_da.c' and see that adaregister() looks at both quirks and > > IDENTIFY_DEVICE data to determine the logical block size. > > > > So, that leaves the bootstrap code as the remaining question-mark. > > Does anyone what AF-4Kn support looks like there? > > > > CC -hackers. > > Thanks for the clarification. Is there any 4Kn HDDs shopping now? I am > not aware of any. > > BTW I believe UFS and ZFS have proper design for 4K-sectors, but > FreeBSD needs some ecosystem connections to get samples early to test, > incorporate supports and validate for it. Or we will need to wait until > it appears on market and someone got caught into some kind of bugs. > > Regards, > Jia-Shiun. > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers- > unsubscribe@freebsd.org"