-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Linus Torvalds
committed
Oct 13, 2012
1 parent
f033aa2
commit aa7794e
Showing
675 changed files
with
18,565 additions
and
11,736 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,2 @@ | ||
--- | ||
refs/heads/master: e9069f470803eeb5e243a05bc717452c6218bd71 | ||
refs/heads/master: 09a9ad6a1ff86836e5280c39300176c4758bb459 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
41 changes: 41 additions & 0 deletions
41
trunk/Documentation/filesystems/nfs/nfsd-admin-interfaces.txt
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
Administrative interfaces for nfsd | ||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|
||
Note that normally these interfaces are used only by the utilities in | ||
nfs-utils. | ||
|
||
nfsd is controlled mainly by pseudofiles under the "nfsd" filesystem, | ||
which is normally mounted at /proc/fs/nfsd/. | ||
|
||
The server is always started by the first write of a nonzero value to | ||
nfsd/threads. | ||
|
||
Before doing that, NFSD can be told which sockets to listen on by | ||
writing to nfsd/portlist; that write may be: | ||
|
||
- an ascii-encoded file descriptor, which should refer to a | ||
bound (and listening, for tcp) socket, or | ||
- "transportname port", where transportname is currently either | ||
"udp", "tcp", or "rdma". | ||
|
||
If nfsd is started without doing any of these, then it will create one | ||
udp and one tcp listener at port 2049 (see nfsd_init_socks). | ||
|
||
On startup, nfsd and lockd grace periods start. | ||
|
||
nfsd is shut down by a write of 0 to nfsd/threads. All locks and state | ||
are thrown away at that point. | ||
|
||
Between startup and shutdown, the number of threads may be adjusted up | ||
or down by additional writes to nfsd/threads or by writes to | ||
nfsd/pool_threads. | ||
|
||
For more detail about files under nfsd/ and what they control, see | ||
fs/nfsd/nfsctl.c; most of them have detailed comments. | ||
|
||
Implementation notes | ||
^^^^^^^^^^^^^^^^^^^^ | ||
|
||
Note that the rpc server requires the caller to serialize addition and | ||
removal of listening sockets, and startup and shutdown of the server. | ||
For nfsd this is done using nfsd_mutex. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
CPU cooling APIs How To | ||
=================================== | ||
|
||
Written by Amit Daniel Kachhap <amit.kachhap@linaro.org> | ||
|
||
Updated: 12 May 2012 | ||
|
||
Copyright (c) 2012 Samsung Electronics Co., Ltd(http://www.samsung.com) | ||
|
||
0. Introduction | ||
|
||
The generic cpu cooling(freq clipping) provides registration/unregistration APIs | ||
to the caller. The binding of the cooling devices to the trip point is left for | ||
the user. The registration APIs returns the cooling device pointer. | ||
|
||
1. cpu cooling APIs | ||
|
||
1.1 cpufreq registration/unregistration APIs | ||
1.1.1 struct thermal_cooling_device *cpufreq_cooling_register( | ||
struct cpumask *clip_cpus) | ||
|
||
This interface function registers the cpufreq cooling device with the name | ||
"thermal-cpufreq-%x". This api can support multiple instances of cpufreq | ||
cooling devices. | ||
|
||
clip_cpus: cpumask of cpus where the frequency constraints will happen. | ||
|
||
1.1.2 void cpufreq_cooling_unregister(struct thermal_cooling_device *cdev) | ||
|
||
This interface function unregisters the "thermal-cpufreq-%x" cooling device. | ||
|
||
cdev: Cooling device pointer which has to be unregistered. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.