I am working on linux-3.7.6/kernel/sched/core.c where in schedule() function I have to record the pid's and tgid's for processes and have to show the recorded values to user space.
I am trying to use the mamp() functionality provided in linux-kernel.
As we call mmap() in user-space we try to map virtual memory area of user-space process to the memory in the kernel-space.
the definition of mamp() inside kernel is done in my kernel module which try to allocate some memory in pages & maps it during mmap system call.
Published at LXer:
The kernel has historically been developed independently of anything that runs in user space. The well-defined kernel ABI, built around the POSIX standard, has allowed for a nearly absolute separation between the kernel and the rest of the system. Linux is nearly unique, however, in its division of kernel and user-space development.
This is my first post so please let me know if there is any mistake from .
My aim is to get approx 150MBytes of data transfer from KERNEL to user space.
Hello everyone,
I wondering if it's possible to create a package that can automatically increase disk quota when 90% of disk space is being used every month?
For example:
A User has been allocated 1000MB of disk quota, when this User has been used 90% (900MB) of his quota space next month will be allocated 500MB more.
Hi all
i have few question relating to linux kernel memory here are the questions
1) Can Kernel space access user space memory yes or no ?
if no what happens when kernel space tries to access user space memory
2) Can Device memory(character device/chipset on the hardware board) be
mapped to user space ?
Cheers
I am finishing up project for OS class and can't figure several things that have to do with SAFELY copying data from user-space into kernel and back from kernel into user space, and how to properly discard this information.
Say I have several system calls:
//copies data into kernel space
long sys_into(void __user *data, long length);
// copies data into user space
long sys_from(void __user *dat
(This question is focussed towards bypassing the kernel for receiving/sending TCP and UDP packets- identical to the techniques which companies like solarflare provide)
I think this question could be worded two ways: what actually needs to be implemented in the user space" to achieve kernel bypass?
I have opened a device driver with a 16 KB kernel space using dma_alloc_coherent.
I have a user program which has 10 KB of data which is in a buffer created by malloc.
now when I do a fwrite in which I call copy_from_user to copy the data from user space to kernel space after which the starting address is given to a peripheral which picks it up.
Email this page
