From owner-freebsd-fs@freebsd.org Tue Jan 5 17:52:32 2016 Return-Path: Delivered-To: freebsd-fs@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 E12BCA631EE for ; Tue, 5 Jan 2016 17:52:32 +0000 (UTC) (envelope-from eborisch@gmail.com) Received: from mail-qk0-x244.google.com (mail-qk0-x244.google.com [IPv6:2607:f8b0:400d:c09::244]) (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 A297015D9 for ; Tue, 5 Jan 2016 17:52:32 +0000 (UTC) (envelope-from eborisch@gmail.com) Received: by mail-qk0-x244.google.com with SMTP id n135so16421844qka.0 for ; Tue, 05 Jan 2016 09:52:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=vUasHaQHTA8wnY0JIqO8eehHs61lTZfF3CHeeLiWskE=; b=T1PfWDUQ5pvzvG5fkKe4r1iWxTGsMuEeetB/4vyLeBK12M21553A8yb1jx+2mmYB2i 5tfHBClXqwINb1/FkHrijs0NHIj99zy9nogG9ypIEeNju8CrMKcxCVqsmsi/D+VATn71 bBloNDjwD2H/2WcLtKe3+6FkGyscqPc6C8ga5yQGnTOi0efycL2nbdF6ItYfsaSQx6X/ pXKJpyelqMsGrBc7b5i3eUURbJwPC6xUtkiCNi88PKA2NQKVlLr0PrpnJPvMj8W5oEB4 Z9lwzPz4DdnkRdEQ1ewMZ8APvZaZHwBpq7e/7inwWTcl/FsWTIBaIrozCVPDAYsFFe1C B78Q== MIME-Version: 1.0 X-Received: by 10.55.73.6 with SMTP id w6mr49342004qka.82.1452016351817; Tue, 05 Jan 2016 09:52:31 -0800 (PST) Received: by 10.55.22.75 with HTTP; Tue, 5 Jan 2016 09:52:31 -0800 (PST) In-Reply-To: <568BFB63.5090203@aldan.algebra.com> References: <8291bb85-bd01-4c8c-80f7-2adcf9947366@email.android.com> <5688D3C1.90301@aldan.algebra.com> <495055121.147587416.1451871433217.JavaMail.zimbra@uoguelph.ca> <568A047B.1010000@aldan.algebra.com> <20160105143542.X1191@besplex.bde.org> <568B574A.7010603@aldan.algebra.com> <568BFB63.5090203@aldan.algebra.com> Date: Tue, 5 Jan 2016 11:52:31 -0600 Message-ID: Subject: Re: Mb vs. MB (Re: NFS reads vs. writes) From: "Eric A. Borisch" To: "Mikhail T." Cc: Matt Churchyard , Bruce Evans , freebsd-fs Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jan 2016 17:52:33 -0000 On Tue, Jan 5, 2016 at 11:20 AM, Mikhail T. wro= te: > On 05.01.2016 05:45, Matt Churchyard wrote: >> You have a different book to most then. >> I've always understood 'b' to mean bits, and 'B' to mean bytes. While ev= eryone on here will understand what you were trying to say in context, give= n purely that number, I would expect most people to interpret it as 90+Mb/s= =3D ~11+MB/s. That is not what you meant, hence why Bruce said be careful = with the units. > I've always found "megabit" to be a useless unit, owning its entire > existence to marketing liars trying to make their wares have more > impressive numbers. Unless the conversation is about information theory, > or CPU-registers and bitfields, any mention of "bit" is useless and > misleading. To (hopefully) end this off-topic discussion, there is a standard, and b =3D=3D bits, and B =3D=3D bytes (usually 8 * b). https://en.wikipedia.org/wiki/IEEE_1541-2002 [...] bit (symbol 'b'), a binary digit; byte (symbol 'B'), a set of adjacent bits (usually, but not necessarily, eight) operated on as a group; [...] It is terribly important ( =3D=3D not useless ) in digital communications, where bits are the basic unit of transferred data, distinct from the signaling rate (bd), but I digress... - Eric