MESSAGE
DATE | 2015-02-01 |
FROM | Ruben Safir
|
SUBJECT | Re: [LIU Comp Sci] DMA memory and CPU activity
|
From owner-learn-outgoing-at-mrbrklyn.com Sun Feb 1 18:44:52 2015 Return-Path: X-Original-To: archive-at-mrbrklyn.com Delivered-To: archive-at-mrbrklyn.com Received: by mrbrklyn.com (Postfix) id F2EB6161191; Sun, 1 Feb 2015 18:44:51 -0500 (EST) Delivered-To: learn-outgoing-at-mrbrklyn.com Received: by mrbrklyn.com (Postfix, from userid 28) id DE4C91612E1; Sun, 1 Feb 2015 18:44:51 -0500 (EST) Delivered-To: learn-at-mrbrklyn.com Received: from mailbackend.panix.com (mailbackend.panix.com [166.84.1.89]) by mrbrklyn.com (Postfix) with ESMTP id 3FBE0161191 for ; Sun, 1 Feb 2015 18:44:51 -0500 (EST) Received: from [10.0.0.19] (unknown [96.57.23.82]) by mailbackend.panix.com (Postfix) with ESMTPSA id F38C213132; Sun, 1 Feb 2015 18:44:50 -0500 (EST) Message-ID: <54CEBA72.4080104-at-panix.com> Date: Sun, 01 Feb 2015 18:44:50 -0500 From: Ruben Safir User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: learn-at-mrbrklyn.com, Samir Iabbassen , learn-at-nylxs.com, Mohammed Ghriga Subject: Re: [LIU Comp Sci] DMA memory and CPU activity References: <54CE533D.1040107-at-my.liu.edu> In-Reply-To: <54CE533D.1040107-at-my.liu.edu> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Sender: owner-learn-at-mrbrklyn.com Precedence: bulk Reply-To: learn-at-mrbrklyn.com
This paragraph makes no sense... I'm sick of wordy textbooks that refuse to be exact in their descriptions. It is like trying to get a graduate degree through a readers digest correspondence programming:
Quote:
Aside from architectural considerations, such as cache, memory, and bus contention, these multicore CPUs appear to the operating system as N standard processors. This characteristic puts pressure on operating system designers—and application programmers—to make use of those processing cores. UNQUOTE
what is N processors, each core or all the cores shared on a chip.
Every dual core system I've seen runs different processes on different cores
top
top - 18:43:07 up 7 days, 3:37, 8 users, load average: 0.28, 0.24, 0.23 Tasks: 132 total, 1 running, 131 sleeping, 0 stopped, 0 zombie %Cpu0 : 28.6/1.4 30[|||||||||||||||| ] %Cpu1 : 16.9/1.4 18[|||||||||| ] GiB Mem : 85.0/3.341 [ ] GiB Swap: 3.3/1.953 [ ]
PID USER PR NI VIRT RES %CPU %MEM TIME+ S COMMAND 1 root 20 0 4.1m 0.5m 0.0 0.0 0:04.70 S init 702 root 20 0 17.5m 0.5m 0.0 0.0 0:00.36 S `- udevd 2132 root 20 0 8.7m 0.6m 0.0 0.0 0:00.00 S `- metalog 2133 root 20 0 8.7m 0.1m 0.0 0.0 0:00.00 S `- metalog 2156 root 20 0 259.4m 0.6m 0.0 0.0 0:00.14 S `- rsyslogd 2181 root 20 0 4.1m 0.4m 0.0 0.0 0:05.02 S `- acpid 2222 dbus 20 0 26.8m 1.4m 0.0 0.0 1:42.52 S `- dbus-daemon 2243 root 20 0 394.7m 1.1m 0.0 0.0 0:00.04 S `- console-kit-d+ 2270 polkitd 20 0 356.6m 1.6m 0.0 0.0 0:00.07 S `- polkitd 2272 root 20 0 337.9m 2.7m 0.0 0.1 0:09.26 S `- NetworkManager 2342 root 20 0 14.4m 1.2m 0.0 0.0 0:00.10 S `- dhclient 2314 root 20 0 181.8m 3.6m 0.0 0.1 4:22.88 S `- wicd 2385 root 20 0 106.2m 3.0m 0.0 0.1 1:48.00 S `- wicd-moni+ 2450 root 20 0 28.6m 1.0m 0.0 0.0 0:00.00 S `- lxdm-binary 2493 root 20 0 664.7m 267.2m 2.7 7.8 160:55.41 S `- Xorg.bin 3420 root 20 0 64.1m 0.9m 0.0 0.0 0:00.00 S `- lxdm-sess+
|
|