Sponsored Content
Operating Systems Linux Fedora Is Kernel module is the same as a device driver? Post 302525263 by newlinuxuser1 on Thursday 26th of May 2011 08:02:41 AM
Old 05-26-2011
Corona688,

Thanks! It is VERY nice and useful post! It clears a lot of sky for me!
 

4 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Kernel and Device Driver Programming

I am looking for a guide on how to program for either the Linux or FreeBSD (includes 4.4BSD, NetBSD or OpenBSD) kernel. I would prefer to learn how to write device drivers, but anything would help. If you know, please email me at *removed* or leave a post here Regards, Farhan (0 Replies)
Discussion started by: Farhan
0 Replies

2. Solaris

SUNWglmr -- rasctrl environment monitoring driver for i2c or SCSI device driver ?

I've been researching minimizeing Solaris 8 and found that on the web page http://www.sun.com/bigadmin/content/packagelist/s8u7PkgList/p2.html the package SUNWglmr is listed as "rasctrl environment monitoring driver for i2c, (Root) (32-bit)" while in the document "Solaris 8 minimize-updt1.pdf"... (1 Reply)
Discussion started by: roygoodwin
1 Replies

3. Linux

Linux Device Driver: avoid mem copy from/to user/kernel space

I recently started working with Linux and wrote my first device driver for a hardware chip controlled by a host CPU running Linux 2.6.x kernel. 1. The user space process makes an IOCTL call with pointer to a user memory buffer. 2. The kernel device driver in the big switch-case of IOCTL,... (1 Reply)
Discussion started by: agaurav
1 Replies

4. UNIX for Advanced & Expert Users

Get pointer for existing device class (struct class) in Linux kernel module

Hi all! I am trying to register a device in an existing device class, but I am having trouble getting the pointer to an existing class. I can create a class in a module, get the pointer to it and then use it to register the device with: *cl = class_create(THIS_MODULE, className);... (0 Replies)
Discussion started by: hdaniel@ualg.pt
0 Replies
pthread_get_nice_np(3T) 												   pthread_get_nice_np(3T)

NAME
pthread_get_nice_np(), pthread_set_nice_np() - get or set the nice value of a thread SYNOPSIS
PARAMETERS
thread The thread whose nice value is to be set/retrieved. nice_val Value of nice to be applied to the target thread is returned (get function) or it specifies the new value of nice for thread (set function). DESCRIPTION
These functions are used to set and retrieve the nice value of an individual thread. returns the current nice value setting of the target thread and stores it in nice_val. adds the value of nice_val to the current nice value of the target thread. A thread's nice value is a non-negative number. The system imposes a minimum nice value of 0 and a maximum of 39 with lower nice values providing more favorable scheduling. If calling results in a nice value outside the range of 0 to 39, the value will be set to the nearest limit. A process must have appropriate privileges to lower a thread's nice value. The function allows individual threads in the process to have different nice values. returns the current nice value less 20 and will be in the range -20 to +19. The nice value of only system scope threads can be changed. An attempt to change the nice value of a process-scope thread will result in a return value of Calling on a thread that has a scheduling policy other than will have an effect only when the thread's scheduling policy changes to If a thread calls the system call to create a new process, the new process inherits the process-level nice value. Calling to create a new thread will result in the new thread inheriting the creating thread's nice value. Note If the nice value of the entire process is changed through or all the threads in the process will have their nice values reset to the new process-level nice value. The new process's nice value setting overwrites the old thread's setting. Thus its possible that a thread whose nice value had been set higher than the process-level nice value have its nice value lowered as a result of the process-level re-nicing. RETURN VALUE
Upon successful completion, and return zero. Otherwise, an error number is returned to indicate the error (the variable is not set). ERRORS
If any of the following occur, the and functions return the corresponding error: A process-scope thread was specified. The caller does not have permission to lower the nice value specified in nice_val. No thread could be found corresponding to thread. AUTHOR
and were developed by HP. SEE ALSO
fork(2), nice(2), setpriority(2), pthread_attr_getschedpolicy(3T), pthread_setschedparam(3T). Pthread Library pthread_get_nice_np(3T)
All times are GMT -4. The time now is 07:25 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy