Editing Block (data storage) (section)

== References ==
{{reflist|refs=
<ref name="CNET14">{{cite news |author=<!-- staff writer, no byline --> |title=Available hard drive space, block sizes, and size terminology |newspaper=CNET |date=2009-05-05 |url=http://www.cnet.com/news/available-hard-drive-space-block-sizes-and-size-terminology/ |access-date=2014-04-29}}</ref>
<ref name="Chang">{{cite web |author-last=Chang |author-first=S. K. |title=Physical Structures |work=Captain SK |url=http://people.cs.pitt.edu/~chang/156/08struct.html |access-date=2014-04-29}}</ref>
<ref name="ZFS1">{{cite news |author-first=Rachel |author-last=Balik |title=Bruning Questions: ZFS Record Size |newspaper=Joyent |date=2013-03-29 |url=https://www.joyent.com/blog/bruning-questions-zfs-record-size/ |access-date=2013-03-29}}</ref>
<ref name="ZFS2">{{cite news |author-first=Roch |author-last=Bourbonnais |title=Tuning ZFS recordsize |date=2006-06-07 |newspaper=Oracle |url=https://blogs.oracle.com/roch/tuning-zfs-recordsize}}</ref>
<ref name="Buchholz_1962">{{citation |title=Planning a Computer System – Project Stretch |author-first1=Gerrit Anne |author-last1=Blaauw |author-link1=Gerrit Anne Blaauw |author-first2=Frederick Phillips |author-last2=Brooks, Jr. |author-link2=Frederick Phillips Brooks, Jr. |author-first3=Werner |author-last3=Buchholz |author-link3=Werner Buchholz |editor-first=Werner |editor-last=Buchholz |editor-link=Werner Buchholz |publisher=[[McGraw-Hill Book Company, Inc.]] / The Maple Press Company, York, PA. |lccn=61-10466 |date=1962 |chapter=4: Natural Data Units |pages=39–40 |chapter-url=http://archive.computerhistory.org/resources/text/IBM/Stretch/pdfs/Buchholz_102636426.pdf |access-date=2017-04-03 |url-status=live |archive-url=https://web.archive.org/web/20170403014651/http://archive.computerhistory.org/resources/text/IBM/Stretch/pdfs/Buchholz_102636426.pdf |archive-date=2017-04-03 |quote=[…] Terms used here to describe the structure imposed by the machine design, in addition to ''[[bit]]'', are listed below.<br/>''[[Byte]]'' denotes a group of bits used to encode a character, or the number of bits transmitted in parallel to and from input-output units. A term other than ''[[character (computing)|character]]'' is used here because a given character may be represented in different applications by more than one code, and different codes may use different numbers of bits (i.e., different byte sizes). In input-output transmission the grouping of bits may be completely arbitrary and have no relation to actual characters. (The term is coined from ''[[bite]]'', but respelled to avoid accidental mutation to ''bit''.)<br/>A ''[[word (computer architecture)|word]]'' consists of the number of data bits transmitted in parallel from or to memory in one memory cycle. [[Word size]] is thus defined as a structural property of the memory. (The term ''[[catena (unit)|catena]]'' was coined for this purpose by the designers of the [[Groupe Bull|Bull]] {{ill|Bull Gamma 60{{!}}GAMMA 60|fr|Gamma 60}} computer.)<br/>''Block'' refers to the number of words transmitted to or from an input-output unit in response to a single input-output instruction. Block size is a structural property of an input-output unit; it may have been fixed by the design or left to be varied by the program. […]}}</ref>
}}

[[Category:Articles with example C Sharp code]]
[[Category:Articles with example Python (programming language) code]]
[[Category:Articles with example Rust code]]
[[Category:Computer data storage]]
[[Category:Data transmission]]