Skip to main content

Timeline for Interpret the output of lstopo

Current License: CC BY-SA 3.0

23 events
when toggle format what by license comment
Nov 18, 2016 at 19:46 comment added slm @G-Man - regenerate it as png. I added example code showing this, I hadn't realized that I didn't actually show how to do it.
Nov 18, 2016 at 19:46 history edited slm CC BY-SA 3.0
added 115 characters in body
Nov 18, 2016 at 18:28 comment added G-Man Says 'Reinstate Monica' @slm: I’m trying to make sense of this. Tim says, “I have a lstopo.txt file, output from lstopo, which is a text drawing … how I can view the file properly?” You answer, “view it as a graphical image rather than an ASCII image.”  How?  Are you suggesting that he (re) generate the output as a graphical image by rerunning the lstopo command with --output-format png (or maybe svg)?  Is there any way to convert a text drawing (like the one Tim links to) to a graphical image?
Nov 18, 2016 at 18:27 history edited G-Man Says 'Reinstate Monica' CC BY-SA 3.0
Improved grammar, punctuation, and formatting.
Feb 5, 2014 at 2:37 vote accept Tim
Feb 4, 2014 at 22:13 comment added slm @Tim - if everything has been cleared up, if you could mark this as accepted everyone will know you issues been answered.
Feb 4, 2014 at 21:32 comment added slm @Tim - yes a socket is the i/f.
Feb 4, 2014 at 21:17 comment added Tim Thanks. Is a socket here is the interface between a CPU and the motherboard?
Feb 4, 2014 at 21:05 comment added slm @Tim - does the picture help? Added another picture that shows the 2 sockets with a pullout image of the cores.
Feb 4, 2014 at 21:05 history edited slm CC BY-SA 3.0
added 1 characters in body
Feb 4, 2014 at 21:02 comment added slm @Tim - the "socket" is the actual physical CPU package that plugs into the motherboard.
Feb 4, 2014 at 21:00 comment added Tim Thanks, about 6, Is the "socket" used for connection between the L3 caches and the main memory?
Feb 4, 2014 at 21:00 comment added slm @Tim - did I cover everything?
Feb 4, 2014 at 20:59 history edited slm CC BY-SA 3.0
added 1 characters in body
Feb 4, 2014 at 20:58 comment added slm @Tim About 8. Yes the cores within the same socket can communicate and have intimate shared access to each others memory at the same clock rate (the clock rate of the CPU itself). When they need to access the other CPU's RAM, then these accesses happen as fast as the memory bus can sustain + the number of clock cycles needed by the other CPU to service the request.
Feb 4, 2014 at 20:56 comment added slm @Tim - the numbers are not the same, b/c they're numbering different aspects of the CPU. The cores are just containers that can have 1 or more processing elements w/in them.
Feb 4, 2014 at 20:53 comment added slm @Tim - About 2. Yes. The key thing to keep in mind, is that from the operating system's perspective I have 4 CPUs. These 4 CPUs are not equivalently capable, but the OS doesn't really know this. I has the operator do.
Feb 4, 2014 at 20:53 comment added Tim About 2, Why are their numbers not the same?
Feb 4, 2014 at 20:52 comment added Tim About 8, after reading the wikipedia link, is the node just like a distributed system with two 4-core computers without shared memory between them? Do the two 4-core groups communicate with each other via message passing, just like communiciation within a distributed system?
Feb 4, 2014 at 20:51 comment added Tim About 2, each of your core has two Processing Unit Processors. So does it function, similar to two cores with each core having one Processing Unit Processor, and can be used for parallel computing by two processing elements?
Feb 4, 2014 at 20:47 history edited slm CC BY-SA 3.0
added 488 characters in body
Feb 4, 2014 at 20:45 comment added Tim Thanks! I will keep watch out what you will add. Can you try to answer the questions in 1 about viewing the textural drawing?
Feb 4, 2014 at 20:40 history answered slm CC BY-SA 3.0