Home
last modified time | relevance | path

Searched refs:ran (Results 1 – 22 of 22) sorted by relevance

/linux-4.4.14/Documentation/
Dnumastat.txt17 local_node A process ran on this node and got memory from it.
19 other_node A process ran on this node and got memory from another node.
Dmono.txt59 4) Check that .exe binaries can be ran without the need of a
DDMA-API.txt682 When the code disables itself at runtime this is most likely because it ran
/linux-4.4.14/Documentation/usb/
Dbulk-streams.txt39 streams, or the xHCI driver ran out of memory), or the number of streams the
/linux-4.4.14/Documentation/timers/
Dhrtimers.txt152 the hrtimer implementation details in praxis, and we also ran the posix
153 timer tests in order to ensure specification compliance. We also ran
/linux-4.4.14/drivers/staging/most/Documentation/ABI/
Dsysfs-class-most.txt180 Indicates whether current channel ran out of buffers.
/linux-4.4.14/Documentation/video4linux/
Dradiotrack.txt21 I have a RadioTrack card from back when I ran an MS-Windows platform. After
/linux-4.4.14/tools/perf/Documentation/
Dperf-report.txt81 - cpu: cpu number the task ran at the time of sample
82 - socket: processor socket number the task ran at the time of sample
/linux-4.4.14/Documentation/ABI/stable/
Dsysfs-driver-ib_srp187 request to the target because it ran out of credits. For more
/linux-4.4.14/Documentation/scheduler/
Dsched-stats.txt136 last ran on a different cpu in this domain
/linux-4.4.14/Documentation/development-process/
D3.Early-stage24 the linux-kernel mailing list, where it immediately ran into problems.
/linux-4.4.14/Documentation/RCU/
Dtorture.txt261 o "nt": The number of times rcutorture ran RCU read-side code from
Dstallwarn.txt218 ran and how often it should be expected to run.
/linux-4.4.14/scripts/
Dspelling.txt862 runned||ran
/linux-4.4.14/firmware/keyspan_pda/
Dkeyspan_pda.S986 ;; either we ran out of data, or we copied 64 bytes. r1 has byte count
Dxircom_pgs.S1051 ;; either we ran out of data, or we copied 64 bytes. r1 has byte count
/linux-4.4.14/Documentation/crypto/
Ddescore-readme.txt152 a while later i ran across the great crypt(3) package mentioned above.
/linux-4.4.14/Documentation/filesystems/caching/
Dbackend-api.txt57 This function may return -ENOMEM if it ran out of memory or -EEXIST if the tag
/linux-4.4.14/Documentation/nvdimm/
Dnvdimm.txt707 1. Why not "volume" for instance? "volume" ran the risk of confusing
/linux-4.4.14/kernel/sched/
Dfair.c4091 u64 ran = se->sum_exec_runtime - se->prev_sum_exec_runtime; in hrtick_start_fair() local
4092 s64 delta = slice - ran; in hrtick_start_fair()
/linux-4.4.14/Documentation/trace/
Dftrace.txt813 and it may look like only one CPU ran (the one with the
1429 ran.
/linux-4.4.14/Documentation/virtual/uml/
DUserModeLinux-HOWTO.txt1641 you ran the daemon with no arguments, running the UML on the same
2925 to fix things up. I ran fsck -y, which hung: