Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have a multi-threaded application that currently runs with one thread dedicated to a particular cpu. The system is a dual cpu system that runs without hyperthreading. The dedicated thread does so in order to access a hardware device that must be accessed from a specific cpu.
The dedicated thread acts as a server that takes queued requests from the other threads of the application. This servicing mechanism required locking and signaling. I would like to optimize this app by having each of the threads temporarily dedicate to the appropriate cpu to access the device.
So I have a couple of questions:
1. Is there a lightweight method for a thread to determine which cpu it is currently running on?
2. How immediate is the effect of sched_setaffinity. Is the calling thread guaranteed to be on the requested cpu upon return?
3. If the thread must make a pass through the scheduler to guarantee affinity, is there a fast "resched" system call? (sched_yield is way to slow to be effective)
By the way.. The system is running Fedora Core6 and is therefore running the 2.6 kernel.