AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080924113911.5148c94e@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<mtracy@css.glasshouse.com>,<dl-cstech@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	66E5C2C5D6B149868D4526D79BEAC594@glasshousetech.com
X-Sylpheed-End-Special-Headers: 1
Date: Wed, 24 Sep 2008 11:39:39 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Michael Tracy" <mtracy@css.glasshouse.com>
Cc: "DL-CStech" <dl-cstech@onstor.com>
Subject: Re: Can anyone direct me to a link/doc with more details of each
 processor?
Message-ID: <20080924113939.06876e85@ripper.onstor.net>
In-Reply-To: <66E5C2C5D6B149868D4526D79BEAC594@glasshousetech.com>
References: <66E5C2C5D6B149868D4526D79BEAC594@glasshousetech.com>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I think the customer is likely asking the wrong question.  What exactly
are they referring to by "load"?  Typically, load only comes from
clients, so ....

On Wed, 24 Sep 2008 09:33:29 -0400 "Michael Tracy"
<mtracy@css.glasshouse.com> wrote:

> Hi all
> Can anyone shed more details as to what each of the processors do.
> I've pasted in an email to show what was given and what the customer
> is looking for.
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> Thank you for your response. However, I am still confused as to =20
> which one is actually handling the network traffic. Is it the NCPU
> of the FP processors? Or do they both handle network traffic but on =20
> different sides of the gateway?
>=20
> We need to know exactly what each one is responsible for so that we =20
> can determine whether the load we are seeing is coming from our
> local LAN side or on the SAN side.
>=20
> Thank you for your help on this,
> Allen Rongone
>=20
> On Sep 23, 2008, at 3:42 PM, Call Center TSE wrote:
>=20
> > Allen,
> >
> > NCPU is the Network CPU (a.k.a. TxRx0).  FP is the File Processor. =20
> > The statement, "NCPU processes (because it is a CPU) network =20
> > transport traffic and that the "FPs handle file system traffic" =20
> > because they are File processors are both correct. File Processor =20
> > (FP) handles IP processing and Network File protocols among other =20
> > things is not ambiguous. The command 'stats show ldavg' will =20
> > display the CPU load averages for TxRx and file processing CPUs. =20
> > The stats show ldavg command tracks information for the amount of =20
> > load on each of the following processors:
> >
> > =E2=80=A2 the NCPU, which processes transport traffic
> > =E2=80=A2 the ACPU, which processes the bulk of the CIFS and NFS traffic
> > =E2=80=A2 the FP1 and FP2 CPUs, which processes the file system traffic
> > =E2=80=A2 the FC CPU, which processes the SCSI traffic
> >
> > Note!
> > The SSC is not in the main data path, so the load on SSC CPUs is =20
> > not displayed.
> > For these processors, the load average displays a value between =20
> > zero (0) and one (1) that indicates
> > how loaded each processor is. Zero indicates that the processors =20
> > have no load; one indicates that the processor is at full load;
> > and a decimal value between 0 and 1 indicates the percentage of
> > load on the processors. For example, a value of .60 indicates a 60%
> > load. The stats show ldavg command gathers the processor loads by
> > using a polling model. Each polling interval is approximately 1 to
> > 2 seconds long. The stats show ldavg command is useful for =20
> > determining which CPUs are more busy or less busy for any given =20
> > user load.
> >
> > I hope this helps to answer your question.
> >
> > Thank you,
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> Can anyone direct me to a link/doc with more details of each
> processor?
>=20
> Michael
