Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
Bread for the World

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
Copyright Info
Terms of Use
Privacy Info
Masthead / Impressum
Your Account

Private Messages

News Archive
Submit News
User Articles
Web Links


The Web

Who's Online
There are currently, 69 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here



Current HOWTO: Linux SMP HOWTO

Linux SMP HOWTO: Glossary Next Previous Contents

9. Glossary

9.1 Definitions

  • SMP Symmetric Multi-Processors.
  • UP Uni-Processor: system with one processor.
  • APIC Advanced Programmable Interrupt Controler.
  • thread A thread is a processor activity in a process. The same process can have multiple threads. Those threads share the process address space and can therefore share data.
  • pthread Posix thread, threads defined by the Posix standard.
  • process Program in execution, with its environment.
  • MTRR Memory Type Range Register
  • APM Advanced Power Management.
  • FPU Floating Point Unit. Also called arithmetic co-processor.
  • IRQ Interrupt ReQuest.
  • EBDA Extended BIOS Data Area.
  • ACPI Advanced Configuration and Power Interface.
  • oops Internal kernel error.
  • Cluster Group of computers that achieve a common computation (also known as Beowulf within the Linux community).

9.2 Concepts

  • Data Races

    A data race happens when to processes want to modify a shared variable concurrently without protecting themselves from the effect of the other process.

    Let A a shared variable. Let P1 and P2 two processes that access this variable. Those two processes are making the same following operation: "read A in tmp variable (local to the precess); do tmp = tmp + 1 ; write tmp in A". If the A variable is not protected by a lock, resulting executions could not correspond to what is espected. For example, here is two examples if one do not lock A:

    case #1:
    P1: read A -> tmp1 (so tmp1 is 0)
    P2: read A -> tmp2 (so tmp2 is 0)
    P1: tmp1 = tmp1 + 1 (so tmp1 is 1)
    P2: tmp2 = tmp2 + 1 (so tmp2 is 1)
    P1: tmp1 -> write A (so A is 1)
    P2: tmp2 -> write A (so A is 1)

    case #2:
    P1: read A -> tmp1 (so tmp1 is 0)
    P1: tmp1 = tmp1 + 1 (so tmp1 is 1)
    P1: tmp1 -> write A (so A is 1)
    P2: read A -> tmp2 (so tmp2 is 1)
    P2: tmp2 = tmp2 + 1 (so tmp2 is 2)
    P2: tmp2 -> write A (so A is 2)

    To avoid this kind of problem, one uses a lock:

    P1: lock A
    P1: read A -> tmp1 (so tmp1 is 0)
    P2: lock A (so P2 is blocked)
    P1: tmp1 = tmp1 + 1 (so tmp1 is 1)
    P1: tmp1 -> write A (so A is 1)
    P1: unlock A (so P2 is unblocked)
    P2: read A -> tmp2 (so tmp2 is 1)
    P2: tmp2 = tmp2 + 1 (so tmp2 is 2)
    P2: tmp2 -> write A (so A is 2)
    P2: unlock A

  • Deadlock

    This is an inter-blocking that occurs when two processes want to access at shared variables mutually locked. For example, let A and B two locks and P1 and P2 two processes:

    P1: lock A
    P2: lock B
    P1: lock B (so P1 is blocked by P2)
    P2: lock A (so P2 is blocked by P1)
    Process P1 is blocked because it is waiting for the unlocking of B variable by P2. However P2 also needs the A variable to finish its computation and free B. So we have a deadlock.

    In this example, the problem is very simple. But imagine what can happen in a 2 millions of lines of code (like the linux kernel) with hundreds of locks. :-)

Next Previous Contents

The Linux Tutorial completely respects the rights of authors and artists to decide for themselves if and how their works can be used, independent of any existing licenses. This means if you are the author of any document presented on this site and do no wish it to be displayed as it is on this site or do not wish it to be displayed at all, please contact us and we will do our very best to accommodate you. If we are unable to accommodate you, we will, at your request, remove your document as quickly as possible.

If you are the author of any document presented on this site and would like a share of the advertising revenue, please contact us using the standard Feedback Form.


More information about the site can be found in the FAQ



Security Code
Security Code
Type Security Code

Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!

Amazon Wish List

Did You Know?
The Linux Tutorial welcomes your suggestions and ideas.


Tell a Friend About Us

Bookmark and Share

Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.53 Seconds