MESSAGE
DATE | 2014-12-06 |
FROM | Maneesh Kongara
|
SUBJECT | Re: [LIU Comp Sci] Parity Bit Algebra
|
From owner-learn-outgoing-at-mrbrklyn.com Sat Dec 6 18:09:49 2014 Return-Path: X-Original-To: archive-at-mrbrklyn.com Delivered-To: archive-at-mrbrklyn.com Received: by mrbrklyn.com (Postfix) id BD18A16007B; Sat, 6 Dec 2014 18:09:49 -0500 (EST) Delivered-To: learn-outgoing-at-mrbrklyn.com Received: by mrbrklyn.com (Postfix, from userid 28) id A228516112F; Sat, 6 Dec 2014 18:09:49 -0500 (EST) Delivered-To: learn-at-mrbrklyn.com Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by mrbrklyn.com (Postfix) with ESMTP id B62E616007B for ; Sat, 6 Dec 2014 18:09:48 -0500 (EST) Received: by mail-qc0-f172.google.com with SMTP id m20so2142578qcx.3 for ; Sat, 06 Dec 2014 15:09:48 -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 :content-type; bh=WBEHOezwhb5RUSDS6E8W2k+APtM8wcxxXf930PeLSQk=; b=ANMZBXYzImT621jhiONjwzduPwGjHiNZ3cyW0kqsYj9vQxqdAGMixLVvPxG8226/kc powWpv745wjSE6K+4VN5RGqNbkIsdm7JCc5UtW15xqJppS8ZvIFbgAuL+5QLR6RW+UyX RRM03+DWvCkHPIEwkznNRMuz0/HgeWvpHYNrtoEg7i9GwGDX2DmPu+zQciSKCLo5IaeI atmuzUV/Z9GkkZmOAxJ9PiYhZAsoObqltTKy6mCJfxWfQQwE4wlXXkuFf7xW+4wRC+bh 4OOqzg/JqUX7hj4EIZacWs5DfYhu77ISFCcvUPc2SM//EeRW0trxaO1SCi3Zk+e+SsWk jpNw== MIME-Version: 1.0 X-Received: by 10.140.89.200 with SMTP id v66mr37565234qgd.85.1417907388237; Sat, 06 Dec 2014 15:09:48 -0800 (PST) Received: by 10.141.1.136 with HTTP; Sat, 6 Dec 2014 15:09:48 -0800 (PST) Received: by 10.141.1.136 with HTTP; Sat, 6 Dec 2014 15:09:48 -0800 (PST) In-Reply-To: <54838C85.60705-at-panix.com> References: <54838832.6010205-at-panix.com> <54838C85.60705-at-panix.com> Date: Sat, 6 Dec 2014 18:09:48 -0500 Message-ID: Subject: Re: [LIU Comp Sci] Parity Bit Algebra From: Maneesh Kongara To: learn-at-mrbrklyn.com Content-Type: multipart/alternative; boundary=001a11c11b50334dfd0509944a86 Sender: owner-learn-at-mrbrklyn.com Precedence: bulk Reply-To: learn-at-mrbrklyn.com
--001a11c11b50334dfd0509944a86 Content-Type: text/plain; charset=UTF-8
Preliminary work as in answers to the other questions of the assignment? On Dec 6, 2014 6:08 PM, "Ruben Safir" wrote:
> On 12/06/2014 10:52 PM, Maneesh Kongara wrote: > > Thanks so much for sharing Mr Rubin. Have you completed the assignment? > > On Dec 6, 2014 5:49 PM, "Ruben Safir" wrote: > > Not even looked at it outside of the library. I'm burning up trying to > catch up. Do you have some preliminary work? > > I did give it throught. Part of the solution must have to do with the > Comp + 2 binary > > I can't even find my notes... > > >> This is from theidiscussion of Raid 3 Stallings Text which the slide > >> come from. It is related to the problem you asked about the parity bit > >> calculation for the Hamming Code > >> > >> Not the methodology for logical calculation, it is straight math > >> > >> Note that X is XOR for whatever UFT reason > >> > >> > >> REDUNDANCY In the event of a drive failure, the parity drive is accessed > >> and data is reconstructed from the remaining devices. Once the failed > >> drive is replaced, the missing data can be restored on the new drive and > >> operation resumed. > >> > >> Data reconstruction is simple. Consider an array of five drives in which > >> X0 through X3 contain data and X4 is the parity disk.The parity for the > >> ith bit is calculated as follows: > >> > >> X4(i) = X3(i) { X2(i) { X1(i) { X0(i) > >> > >> where { is exclusive-OR function. > >> > >> Suppose that drive X1 has failed. If we add X4(i) { X1(i) to both sides > >> of the preceding equation, we get > >> > >> X1(i) = X4(i) { X3(i) { X2(i) { X0(i) > >> > >> > >> file:///home/ruben/william stallings - computer organization and > >> architecture designing for performance (8th edition).pdf > >> > >> Page 202 > >> > >> > >> > >> http://www.nylxs.com/images/raid3_parity_math.png > >> > >> Ruben > >> > >
--001a11c11b50334dfd0509944a86 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Preliminary work as in answers to the other questions of the= assignment?
On Dec 6, 2014 6:08 PM, "Ruben Safir" = < mrbrklyn-at-panix.com> wrote:= 0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 12/06/2014 10:52= PM, Maneesh Kongara wrote:
> Thanks so much for sharing Mr Rubin. Have you completed the assignment= ?
> On Dec 6, 2014 5:49 PM, "Ruben Safir" <mrbrklyn-at-panix.com">mrbrklyn-at-panix.com> wrote:
Not even looked at it outside of the library.=C2=A0 I'm burning up tryi= ng to
catch up.=C2=A0 Do you have some preliminary work?
I did give it throught.=C2=A0 Part of the solution must have to do with the=
Comp + 2 binary
I can't even find my notes...
>> This is from theidiscussion of Raid 3 Stallings Text which the sli= de
>> come from.=C2=A0 It is related to the problem you asked about the = parity bit
>> calculation for the Hamming Code
>>
>> Not the methodology for logical calculation, it is straight mathr> >>
>> Note that X is XOR for whatever UFT reason
>>
>>
>> REDUNDANCY In the event of a drive failure, the parity drive is ac= cessed
>> and data is reconstructed from the remaining devices. Once the fai= led
>> drive is replaced, the missing data can be restored on the new dri= ve and
>> operation resumed.
>>
>> Data reconstruction is simple. Consider an array of five drives in= which
>> X0 through X3 contain data and X4 is the parity disk.The parity fo= r the
>> ith bit is calculated as follows:
>>
>> X4(i) =3D X3(i) { X2(i) { X1(i) { X0(i)
>>
>> where { is exclusive-OR function.
>>
>> Suppose that drive X1 has failed. If we add X4(i) { X1(i) to both = sides
>> of the preceding equation, we get
>>
>> X1(i) =3D X4(i) { X3(i) { X2(i) { X0(i)
>>
>>
>> file:///home/ruben/william stallings - computer organization andr> >> architecture designing for performance (8th edition).pdf
>>
>> Page 202
>>
>>
>>
>> et=3D"_blank">http://www.nylxs.com/images/raid3_parity_math.png
>>
>> Ruben
>>
--001a11c11b50334dfd0509944a86--
|
|