From owner-freebsd-current@freebsd.org Sun Apr 10 12:59:05 2016 Return-Path: <owner-freebsd-current@freebsd.org> Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 598A8B09A4D for <freebsd-current@mailman.ysv.freebsd.org>; Sun, 10 Apr 2016 12:59:05 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1EE881D5A for <freebsd-current@freebsd.org>; Sun, 10 Apr 2016 12:59:05 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-oi0-x232.google.com with SMTP id y204so180850883oie.3 for <freebsd-current@freebsd.org>; Sun, 10 Apr 2016 05:59:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=r65aODI08mpsQHNyONXXYJA3Ek6EJy0yTf6Q5QL0lmc=; b=bYCBb/i9zW44VQWBqZPx0EopEtzx4zmTm1llDt0lrhbegCu2DUwg0DAavC5E0/YERL m85p5Sfrzpw+/cf5CMDTVa+93IqEfpL3y/OXtV1+j6i7KzcThik8g/gYztSocLkwCSj5 nwM8vXgiXNi5vwpOSAddWwSlrbrzuJ6kC4CuXMAjeP1ZeOhPdQe1vFCHH1Cphro3WKiT RzPPLLMOyl9Bxsxkc8cG4utho9r0euVRWa3O5ULSfARw1OdynEzBGZmF49PfSilUwZZ7 pvbkodLmSuzkivwui8rH3YNZWsLL1qfw6KfSxSmzLJ9t4weYuRtDDCjiKqpYNc8WoNQj VJVg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=r65aODI08mpsQHNyONXXYJA3Ek6EJy0yTf6Q5QL0lmc=; b=lj4i7l+oRIutbaJcGjGep6NYmVRW5uW2Uaw3dY1hK+p2+BPuFr/ShNUfwtGbkh+CfZ e+GbFnjNZpmlE9MuRPPPW5pqzDnoVdfEH8IFa7nSqoR71JhyPDbmPD15UYMJE2wX6cGB cLkmFwEPDo1/m+IZ4a7IG64HXnc5PvtR49GOXzs/Cr70DDpclyayf25rypK4Dtsds0tT t1e80Lv2HpCJcA0mDHLqT0bnSpw8bPweoheSWRMj5xUYCIxW005cCxe02e5TkdvkQsZW /uDtZbme8ikFVkg//ZOyov8JT17wu6htjPseyr527RZRJ6lEIouPkmAryClSicU+sIsV NSew== X-Gm-Message-State: AD7BkJLvnd8OY1DrxSP3oAPWYX97gIcXzB/6zhxoj33oEliqQIoz1TWknuyTcpMYII/b8ae3q1Jc8qIGEIlHpQ== MIME-Version: 1.0 X-Received: by 10.202.220.87 with SMTP id t84mr7704055oig.57.1460293144400; Sun, 10 Apr 2016 05:59:04 -0700 (PDT) Sender: asomers@gmail.com Received: by 10.202.64.138 with HTTP; Sun, 10 Apr 2016 05:59:04 -0700 (PDT) In-Reply-To: <20160410155621.82b751fa79f94ab2472264d7@dec.sakura.ne.jp> References: <20160410155621.82b751fa79f94ab2472264d7@dec.sakura.ne.jp> Date: Sun, 10 Apr 2016 06:59:04 -0600 X-Google-Sender-Auth: 4LjaxWHnDO1ZmN0mJ9plki2Wa70 Message-ID: <CAOtMX2jXcQJv2VPR-j=aAgPWA_sJQ_TO7TfVpbmEmk6u9B1YYQ@mail.gmail.com> Subject: Re: Question about cam 4K quirks From: Alan Somers <asomers@freebsd.org> To: Tomoaki AOKI <junchoon@dec.sakura.ne.jp> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org> Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Discussions about the use of FreeBSD-current <freebsd-current.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/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: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sun, 10 Apr 2016 12:59:05 -0000 On Sun, Apr 10, 2016 at 12:56 AM, Tomoaki AOKI <junchoon@dec.sakura.ne.jp> wrote: > Hi. Maybe freebsd-hardware list would be the right place, but it's not > so active. :-( > > Is 4K quirks needed for every HDDs/SSDs having physical sector size > 4096? > > If so, I would be able to provide patch for Crucial M550 and MX200. > (Possibly covers other models [BX200 etc.] by abstraction.) > > M550(1TB): device model Crucial CT1024M550SSD1 > firmware revision MU01 > MX200(1TB): device model Crucial CT1024MX200SSD1 > firmware revision MU03 > -> Abstracted with "Crucial CT*SSD*" or "Crucial CT*", as the part > "1024" should vary with its capacity and can be 3 to 4 digits > for now. I tried the former and confirmed "quirks=0x1<4K>" > appears, which doesn't appear without adding the entry. > > > If not, is it sufficient if `camcontrol identify <device>` states > "physical 4096" on "sector size" line for everything in kernel and > related components (i.e., zfs-related ones)? > > > Regards. You only need quirk entries if the device fails to identify its physical size correctly. If "camcontrol identify" states "physical 4096", then you're probably ok, but it's not the best place to ask. "camcontrol identify" asks the device directly, whereas "diskinfo -v" asks the kernel. If "diskinfo -v" says "4096 stripesize" then you're definitely ok. -Alan