| /linux-2.6.39/Documentation/scheduler/ |
| D | sched-stats.txt | 7 12 which was in the kernel from 2.6.13-2.6.19 (version 13 never saw a kernel
38 1) # of times sched_yield() was called
42 3) # of times schedule() was called
46 5) # of times try_to_wake_up() was called
47 6) # of times try_to_wake_up() was called to wake up the local cpu
69 1) # of times in this domain load_balance() was called when the
70 cpu was idle
72 the load did not require balancing when the cpu was idle
74 more tasks and failed, when the cpu was idle
76 load_balance() in this domain when the cpu was idle
[all …]
|
| D | sched-nice-design.txt | 7 Unfortunately that was not that easy to implement under the old
9 support was historically coupled to timeslice length, and timeslice
10 units were driven by the HZ tick, so the smallest timeslice was 1/HZ.
37 changing the ABI to extend priorities was discarded early on.)
44 this was long ago when hardware was weaker and caches were smaller, and
56 coupling to timeslices and granularity it was not really viable.
59 about Linux's nice level support was its assymetry around the origo
75 depend on the nice level of the parent shell - if it was at nice -10 the
76 CPU split was different than if it was at +5 or +10.
78 A third complaint against Linux's nice level support was that negative
[all …]
|
| /linux-2.6.39/Documentation/filesystems/ |
| D | locks.txt | 14 The old flock(2) emulation in the kernel was swapped for proper BSD
29 Because sendmail was unable to use the old flock() emulation, many sendmail
31 for example. This gave rise to some other subtle problems if sendmail was
46 race and deadlock conditions that the current solution was the only
57 was prior to this release a general configuration option that was valid for
59 least of which was the ability to freeze an NFS server by asking it to read
|
| D | dnotify.txt | 15 DN_ACCESS A file in the directory was accessed (read)
16 DN_MODIFY A file in the directory was modified (write,truncate)
17 DN_CREATE A file was created in the directory
18 DN_DELETE A file was unlinked from directory
19 DN_RENAME A file in the directory was renamed
|
| /linux-2.6.39/Documentation/arm/nwfpe/ |
| D | README | 4 The majority of the code was written by me, Scott Bambrough It is
6 where required. It was written quickly, with a goal of implementing a
17 Another choice I made was in the file structure. I have attempted to
30 SoftFloat to the ARM was done by Phil Blundell, based on an earlier
57 SoftFloat was written by John R. Hauser. This work was made possible in
59 1947 Center Street, Berkeley, California 94704. Funding was partially
61 original version of this code was written as part of a project to build
|
| /linux-2.6.39/fs/reiserfs/ |
| D | README | 40 fair, ask. (Last I spoke with him Richard was contemplating how best
84 Hans Reiser was the project initiator, primary architect, source of all
88 Vladimir Saveljev was one of the programmers, and he worked long hours
91 was quite remarkable. I don't think that money can ever motivate someone
99 substantial portion of the total code. He realized that there was a
106 tried to put me in a position where I was forced into giving control
109 really force takeovers of sole proprietorships.) This was something
111 why we should do what we do, or why innovation was possible in
112 general, but he was sure that he ought to be controlling it. Every
113 innovation had to be forced past him while he was with us. He added
[all …]
|
| /linux-2.6.39/Documentation/scsi/ |
| D | sym53c500_cs.txt | 2 package, and was written by Tom Corner (tcorner@via.at). A rewrite was
8 All the USE_BIOS code has been ripped out. It was never used, and could
14 The Symbios Logic 53c500 chip was used in the "newer" (circa 1997) version
|
| D | dpti.txt | 23 * The original linux driver was ported to Linux by Karen White while at
24 * Dell Computer. It was ported from Bob Pasteur's (of DPT) original
31 * The driver was originally ported to linux version 2.0.34
34 * This was the first full GPL version since the last version used
|
| /linux-2.6.39/drivers/staging/wlags49_h2/ |
| D | README.ubuntu | 42 For the test Station mode was used with WEP. The driver is supposed
65 WPA and AP mode should also work; note however that WPA was experimental
85 change which checked a variable that was not changed in HCF anymore.
86 -- Used on WEP but setting keys via SIOCSIWENCODEEXT was not supported
89 The major problem was the order in which calls can be made. The original
94 after "close", which was not expected. One of the problems was enable/
98 this was solved most HCF_ASSERTS went away.
102 At a few times recovery code was added; when the card starts to
127 The following was mailed by Agere to Andrey Borzenkov about this:
159 The Linux driver architecture was based on two modules, the MSF (Module
[all …]
|
| /linux-2.6.39/Documentation/usb/ |
| D | error-codes.txt | 59 -EPERM Submission failed because urb->reject was set.
61 -EHOSTUNREACH URB was rejected because the device is suspended.
82 -ENOENT URB was synchronously unlinked by usb_unlink_urb
99 driver cannot tell whether there was a protocol
109 completed, and no other error was reported by HC.
122 -EOVERFLOW (*) The amount of data returned by the endpoint was
127 specified buffer, and URB_SHORT_NOT_OK was set in
130 -ENODEV Device was removed. Often preceded by a burst of
139 -ECONNRESET URB was asynchronously unlinked by usb_unlink_urb
|
| D | persist.txt | 20 device is still attached or perhaps it was removed and a different
30 If the kernel wants to believe that your USB keyboard was unplugged
31 while the system was asleep and a new keyboard was plugged in when the
37 been unplugged while the system was suspended. If you had a mounted
40 root filesystem was located on the device, since your system will
46 was asleep, on many systems during the initial stages of wakeup the
57 has happened; look for lines saying "root hub lost power or was reset".
73 not in the expected state during resume (i.e., if the controller was
87 but a USB device was unplugged and then replugged, or if a USB device
|
| /linux-2.6.39/drivers/block/paride/ |
| D | Transition-notes | 36 ps_tq if ps_tq_active was 0.
62 In the first case the thread was already in the area. In the second,
63 the thread was holding pd_lock and found pd_busy not set, which would
64 mean that (2) was already not true.
70 (3) was already not true.
79 pd.c. It means that (4) was already not true.
89 If it was 0 before we tried to acquire pd_lock, (2) would be
108 point, we would have violated either (2.1) (if it was set while ps_set_intr()
109 was acquiring ps_spinlock) or (2.3) (if it was set when we started to
|
| /linux-2.6.39/Documentation/watchdog/ |
| D | watchdog-api.txt | 96 printf("The timeout was set to %d seconds\n", timeout);
98 This example might actually print "The timeout was set to 60 seconds"
105 printf("The timeout was is %d seconds\n", timeout);
127 printf("The pretimeout was is %d seconds\n", timeout);
138 printf("The timeout was is %d seconds\n", timeleft);
162 The machine was last rebooted by the watchdog because the thermal limit was
171 External monitoring relay/source 1 was triggered. Controllers intended for
177 External monitoring relay/source 2 was triggered
185 The last reboot was caused by the watchdog card
195 The watchdog saw a keepalive ping since it was last queried.
|
| /linux-2.6.39/tools/perf/Documentation/ |
| D | perf-sched.txt | 24 was recorded.
26 'perf sched replay' to simulate the workload that was recorded
30 of the workload as it occurred when it was recorded - and can repeat
|
| /linux-2.6.39/arch/arm/mm/ |
| D | tlb-v6.S | 48 mcr p15, 0, r0, c8, c6, 1 @ TLB invalidate D MVA (was 1)
50 mcrne p15, 0, r0, c8, c5, 1 @ TLB invalidate I MVA (was 1)
52 mcr p15, 0, r0, c8, c7, 1 @ TLB invalidate MVA (was 1)
|
| /linux-2.6.39/Documentation/w1/slaves/ |
| D | w1_ds2423 | 24 was successful and CRC matched.
25 If the operation was successful, there is also in the end of each line
32 - 2 bytes for crc16 which was calculated from the data read since the previous crc bytes
34 - crc=YES/NO indicating whether read was ok and crc matched
|
| /linux-2.6.39/arch/m68k/ifpsp060/ |
| D | CHANGES | 33 1) "movep" emulation where data was being read from memory
34 was reading the intermediate bytes. Emulation now only
37 2) "flogn", "flog2", and "flog10" of "1" was setting the
42 mode was pre-decrement or post-increment and the address register
43 was A0 or A1, the address register was not being updated as a result
|
| /linux-2.6.39/Documentation/i2c/ |
| D | fault-codes | 40 transmit mode: some other master was transmitting different
57 Returned by SMBus adapters when the bus was busy for longer
60 or that the reset was attempted but failed.
64 detected before any I/O operation was started. Use a more
90 an I2C device was temporarily not responding, usually it
103 have verified that functionality was supported before it
120 time, and was aborted before it completed.
|
| /linux-2.6.39/Documentation/networking/ |
| D | lapb-module.txt | 136 LAPB_OK LAPB getparms was successful.
148 LAPB_OK LAPB getparms was successful.
150 LAPB_INVALUE One of the values was out of its allowable range.
224 LAPB_OK The LAPB link was terminated normally.
225 LAPB_NOTCONNECTED The remote system was not connected.
226 LAPB_TIMEDOUT No response was received in N2 tries from the remote
237 LAPB_OK The LAPB link was terminated normally by the remote
240 LAPB_NOTCONNECTED The remote system was not connected.
241 LAPB_TIMEDOUT No response was received in N2 tries from the remote
254 file include/linux/netdevice.h) if and only if the frame was dropped
|
| D | skfp.txt | 125 The functionality of the LED's on the FDDI network adapters was
132 With versions of SMT prior to v2.82 a ring up was indicated if the
133 yellow LED was off while the green LED(s) showed the connection
134 status of the adapter. During a ring down the green LED was off and
135 the yellow LED was on.
186 - Synchronization on SMP machines was buggy
|
| /linux-2.6.39/Documentation/mtd/ |
| D | nand_ecc.txt | 5 I felt there was room for optimisation. I bashed the code for a few hours
7 After that the speed was increased by 35-40%.
8 Still I was not too happy as I felt there was additional room for improvement.
10 Bad! I was hooked.
24 not use the right terminology, my coding theory class was almost 30
25 years ago, and I must admit it was not one of my favourites).
153 Therefore without implementing this it was clear that the code above was
260 almost 4 times as much time as the linux driver code. But hey, if it was
438 observation was that this one is only 30% slower (according to time)
441 Well, it was expected not to be easy so maybe instead move to a
[all …]
|
| /linux-2.6.39/fs/affs/ |
| D | Changes | 162 This was fixed before, but somehow got lost.
172 inode if the fs was not an OFS. This bug only shows
173 up if a file was enlarged via truncate() and there
174 was not enough space.
188 - Fixed bug in balloc(): Superblock was not set dirty after
189 the bitmap was changed, so the bitmap wasn't sync'd.
192 zone number was zero, the loop didn't terminate,
250 cache. If a file was extended by means of
303 was calculated and in the one following. This
|
| /linux-2.6.39/drivers/message/i2o/ |
| D | README.ioctl | 53 EFAULT Invalid user space pointer was passed
79 EFAULT Invalid user space pointer was passed
108 EFAULT Invalid user space pointer was passed
143 EFAULT Invalid user space pointer was passed
150 A return value of 0 does not mean that the value was actually
180 EFAULT Invalid user space pointer was passed
187 A return value of 0 does not mean that the value was actually
227 EFAULT Invalid user space pointer was passed
269 EFAULT Invalid user space pointer was passed
306 EFAULT Invalid user space pointer was passed
[all …]
|
| /linux-2.6.39/Documentation/i2o/ |
| D | ioctl | 53 EFAULT Invalid user space pointer was passed
79 EFAULT Invalid user space pointer was passed
108 EFAULT Invalid user space pointer was passed
143 EFAULT Invalid user space pointer was passed
150 A return value of 0 does not mean that the value was actually
180 EFAULT Invalid user space pointer was passed
187 A return value of 0 does not mean that the value was actually
227 EFAULT Invalid user space pointer was passed
269 EFAULT Invalid user space pointer was passed
306 EFAULT Invalid user space pointer was passed
[all …]
|
| /linux-2.6.39/Documentation/ABI/obsolete/ |
| D | proc-pid-oom_adj | 8 this tunable such that its meaning is deprecated. The value was
15 A much more powerful interface, /proc/<pid>/oom_score_adj, was
|