mirrors/linux-stable
1
0
Fork 0
mirror of https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git synced 2024-08-21 08:19:28 +00:00
Code Issues Releases Wiki Activity

Documentation: file handles are now freed

Browse source 
Since file handles are freed, a little amendment to the documentation

Signed-off-by: Federica Teodori <federica.teodori@googlemail.com>
Acked-by: Rik van Riel<riel@redhat.com>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:
Federica Teodori 2011-03-15 16:12:05 -07:00 committed by Linus Torvalds
parent aa4862c38b
commit ca3b78aa16
1 changed files with 8 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
Documentation/sysctl/fs.txt
View file

@ -88,20 +88,19 @@ you might want to raise the limit.
file-max & file-nr: file-max & file-nr:
The kernel allocates file handles dynamically, but as yet it
doesn't free them again.
The value in file-max denotes the maximum number of file- The value in file-max denotes the maximum number of file-
handles that the Linux kernel will allocate. When you get lots handles that the Linux kernel will allocate. When you get lots
of error messages about running out of file handles, you might of error messages about running out of file handles, you might
want to increase this limit. want to increase this limit.
Historically, the three values in file-nr denoted the number of Historically,the kernel was able to allocate file handles
allocated file handles, the number of allocated but unused file dynamically, but not to free them again. The three values in
handles, and the maximum number of file handles. Linux 2.6 always file-nr denote the number of allocated file handles, the number
reports 0 as the number of free file handles -- this is not an of allocated but unused file handles, and the maximum number of
error, it just means that the number of allocated file handles file handles. Linux 2.6 always reports 0 as the number of free
exactly matches the number of used file handles. file handles -- this is not an error, it just means that the
number of allocated file handles exactly matches the number of
used file handles.
Attempts to allocate more file descriptors than file-max are Attempts to allocate more file descriptors than file-max are
reported with printk, look for "VFS: file-max limit <number> reported with printk, look for "VFS: file-max limit <number>