Sponsored Content
Operating Systems Linux SuSE max number of slabs per kernel module (kernel 2.6.17, suse) Post 302160203 by Brendan Kennedy on Monday 21st of January 2008 06:55:45 AM
Old 01-21-2008
max number of slabs per kernel module (kernel 2.6.17, suse)

Hi All,

Is there a max number of slabs that can be used per kernel module? I'm having a tough time finding out that kind of information, but the array 'node_zonelists' (mmzone.h) has a size of 5. I just want to avoid buffer overruns and other bad stuff.

Cheers,
Brendan
 

4 More Discussions You Might Find Interesting

1. Linux

How to convert Linux Kernel built-in module into a loadable module

Hi all, I am working on USB data monitoring on Fedora Core 9. Kernel 2.6.25 has a built-in module (the one that isn't loadable, but compiles and links statically with the kernel during compilation) to snoop USB data. It is in <kernel_source_code>/drivers/usb/mon/. I need to know if I can... (0 Replies)
Discussion started by: anitemp
0 Replies

2. IP Networking

kernel module

Hi All, I need to develop a kernel module which changes the IP address of a package according to its mac address. It would be a sort of L2 Nat. Somebody know if I can do this using netfilter?? Thanks. (2 Replies)
Discussion started by: lagigliaivan
2 Replies

3. Linux

kernel module parameters

Hi, if I install a module with specific parameter, will this parameters applied next time system boots? for exampe, I want to disable InterruptThrottleRate modprobe e1000e InterruptThrottleRate=0 Is this parameter apllied only for this run, or this module will always use this parameter when... (2 Replies)
Discussion started by: Shedon
2 Replies

4. Linux

Unload kernel module at boot time (Debian Wheezy 7.2, 3.2.0-4-686-pae kernel)

Hi everyone, I am trying to prevent the ehci_hcd kernel module to load at boot time. Here's what I've tried so far: 1) Add the following line to /etc/modprobe.d/blacklist.conf (as suggested here): 2) Blacklisted the module by adding the following string to 3) Tried to blacklist the module... (0 Replies)
Discussion started by: gacanepa
0 Replies
QUERY_MODULE(2) 					     Linux Programmer's Manual						   QUERY_MODULE(2)

NAME
query_module - query the kernel for various bits pertaining to modules SYNOPSIS
#include <linux/module.h> int query_module(const char *name, int which, void *buf, size_t bufsize, size_t *ret); DESCRIPTION
query_module() requests information from the kernel about loadable modules. The returned information is placed in the buffer pointed to by buf. The caller must specify the size of buf in bufsize. The precise nature and format of the returned information depend on the opera- tion specified by which. Some operations require name to identify a currently loaded module, some allow name to be NULL, indicating the kernel proper. The following values can be specified for which: 0 Returns success, if the kernel supports query_module(). Used to probe for availability of the system call. QM_MODULES Returns the names of all loaded modules. The returned buffer consists of a sequence of null-terminated strings; ret is set to the number of modules. QM_DEPS Returns the names of all modules used by the indicated module. The returned buffer consists of a sequence of null-terminated strings; ret is set to the number of modules. QM_REFS Returns the names of all modules using the indicated module. This is the inverse of QM_DEPS. The returned buffer consists of a sequence of null-terminated strings; ret is set to the number of modules. QM_SYMBOLS Returns the symbols and values exported by the kernel or the indicated module. The returned buffer is an array of structures of the following form struct module_symbol { unsigned long value; unsigned long name; }; followed by null-terminated strings. The value of name is the character offset of the string relative to the start of buf; ret is set to the number of symbols. QM_INFO Returns miscellaneous information about the indicated module. The output buffer format is: struct module_info { unsigned long address; unsigned long size; unsigned long flags; }; where address is the kernel address at which the module resides, size is the size of the module in bytes, and flags is a mask of MOD_RUNNING, MOD_AUTOCLEAN, etc. that indicates the current status of the module (see the kernel source file include/linux/mod- ule.h). ret is set to the size of the module_info structure. RETURN VALUE
On success, zero is returned. On error, -1 is returned and errno is set appropriately. ERRORS
EFAULT At least one of name, buf, or ret was outside the program's accessible address space. EINVAL Invalid which; or name is NULL (indicating "the kernel"), but this is not permitted with the specified value of which. ENOENT No module by that name exists. ENOSPC The buffer size provided was too small. ret is set to the minimum size needed. ENOSYS query_module() is not supported in this version of the kernel. CONFORMING TO
query_module() is Linux-specific. NOTES
This system call is only present on Linux up until kernel 2.4; it was removed in Linux 2.6. Some of the information that was available via query_module() can be obtained from /proc/modules, /proc/kallsyms, and /sys/modules. SEE ALSO
create_module(2), delete_module(2), get_kernel_syms(2), init_module(2) COLOPHON
This page is part of release 3.25 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. Linux 2007-06-03 QUERY_MODULE(2)
All times are GMT -4. The time now is 07:54 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy