/linux-4.4.14/drivers/net/ethernet/mellanox/mlx4/ |
D | resource_tracker.c | 307 int allocated, free, reserved, guaranteed, from_free; in mlx4_grant_resource() local 322 guaranteed = res_alloc->guaranteed[slave]; in mlx4_grant_resource() 331 if (allocated + count <= guaranteed) { in mlx4_grant_resource() 336 if (guaranteed - allocated > 0) in mlx4_grant_resource() 337 from_free = count - (guaranteed - allocated); in mlx4_grant_resource() 377 int allocated, guaranteed, from_rsvd; in mlx4_release_resource() local 388 guaranteed = res_alloc->guaranteed[slave]; in mlx4_release_resource() 390 if (allocated - count >= guaranteed) { in mlx4_release_resource() 394 if (allocated - guaranteed > 0) in mlx4_release_resource() 395 from_rsvd = count - (allocated - guaranteed); in mlx4_release_resource() [all …]
|
D | mlx4.h | 549 int *guaranteed; member
|
/linux-4.4.14/Documentation/networking/ |
D | netdevices.txt | 57 Note: netif_running() is guaranteed false 92 Notes: netif_queue_stopped() is guaranteed true
|
D | operstates.txt | 80 interrupts. It is guaranteed that only the driver has write access,
|
D | phy.txt | 47 number. These functions are guaranteed not to be called from interrupt
|
D | ip-sysctl.txt | 164 guaranteed if the pool size is less than inet_peer_threshold. 494 It is guaranteed to each TCP socket, even under moderate memory 1909 It is guaranteed to each SCTP socket (but not association) even
|
D | rxrpc.txt | 231 the tag is guaranteed not to be seen again, and so it can be used to pin
|
/linux-4.4.14/Documentation/ABI/testing/ |
D | sysfs-class-scsi_host | 11 guaranteed. The 'isci_id' attribute unambiguously identifies
|
/linux-4.4.14/Documentation/virtual/kvm/ |
D | cpuid.txt | 6 cpuid. This is not always guaranteed to work, since userspace can
|
D | msr.txt | 29 guaranteed to update this data at the moment of MSR write. 117 0 | 24 | multiple cpus are guaranteed to 253 Hypervisor is guaranteed to only modify this least
|
D | hypercalls.txt | 6 guaranteed to be supported.
|
D | timekeeping.txt | 444 synchronization unless it is explicitly guaranteed by the architecture. Even
|
D | api.txt | 43 not cause harm to the host, their actual behavior is not guaranteed by
|
/linux-4.4.14/tools/testing/selftests/powerpc/switch_endian/ |
D | check.S | 11 nop # guaranteed to be illegal in reverse-endian
|
/linux-4.4.14/Documentation/hwmon/ |
D | adc128d818 | 24 Measurements are guaranteed between -55 and +125 degrees. The temperature
|
D | thmc50 | 41 degrees Celsius, and are guaranteed within a range of -55 to +125 degrees.
|
D | lm80 | 37 is unclear about this). Measurements are guaranteed between -55 and
|
D | gl518sm | 39 situation. Measurements are guaranteed between -10 degrees and +110
|
D | lm78 | 38 is above the Overtemperature Shutdown value. Measurements are guaranteed
|
D | lm75 | 74 All temperatures are in degrees Celsius, and are guaranteed within a
|
D | lm83 | 76 accuracy is guaranteed to 3.0 degrees (see the datasheet for more
|
D | w83793 | 105 Only Fan1-5 and PWM1-3 are guaranteed to always exist, other fan inputs and
|
D | coretemp | 42 Correct CPU operation is no longer guaranteed.
|
D | sis5595 | 70 value. Measurements are guaranteed between -55 and +125 degrees, with a
|
D | w83781d | 88 Temperatures are guaranteed within a range of -55 to +125 degrees. The
|
/linux-4.4.14/drivers/mtd/onenand/ |
D | Kconfig | 52 OTP block is fully-guaranteed to be a valid block.
|
/linux-4.4.14/Documentation/ |
D | atomic_ops.txt | 36 are guaranteed to be correct reflecting the initialized value if the 57 all threads are guaranteed to be correct reflecting either the value that has 60 is guaranteed to be readable with atomic_read from another thread. 67 The read is atomic in that the return value is guaranteed to be one of the 80 atomic_set(). This is not uniformly guaranteed, and may change in the future, 318 be guaranteed that no other entity can be accessing the object:
|
D | this_cpu_ops.txt | 214 that are guaranteed to be atomic and then re-enable interrupts. Doing 224 modifies the variable, then RMW actions can not be guaranteed to be 267 If you use the variables as intended, this_cpu_ops() are guaranteed to
|
D | workqueue.txt | 146 more execution contexts are necessary, which in turn is guaranteed 196 have this flag set. The wq is guaranteed to have at least one 227 are now non-reentrant - any work item is guaranteed to be executed by
|
D | memory-barriers.txt | 457 pair is -not- guaranteed to act as a full memory barrier. However, after 459 RELEASE on that same variable are guaranteed to be visible. In other 461 previous critical sections for that variable are guaranteed to have 469 between two CPUs or between a CPU and a device. If it can be guaranteed that 686 ordering is guaranteed only when the stores differ, for example: 774 if control dependencies guaranteed transitivity (which they do not), 1286 However, transitivity is -not- guaranteed for read or write barriers. 1676 barrier after it, depending on the function. It isn't guaranteed to 2025 In contrast, if a wakeup does occur, CPU 2's load from X would be guaranteed 2512 They are guaranteed to be fully ordered with respect to each other. [all …]
|
D | flexible-arrays.txt | 73 flex_array_put() call on an element in that range is guaranteed not to
|
D | circular-buffers.txt | 132 producer and consumer become visible cannot be guaranteed as they are
|
D | assoc_array.txt | 125 These functions are guaranteed not to fail. 460 is guaranteed that none of the leaves in a node will match a slot occupied by a
|
D | robust-futexes.txt | 101 The list is guaranteed to be private and per-thread at do_exit() time,
|
D | media-framework.txt | 135 IDs manually must ensure that all IDs are unique. IDs are not guaranteed to be
|
D | parport-lowlevel.txt | 359 claim is guaranteed to succeed), or choose not to if you don't need it
|
D | DMA-API.txt | 235 are guaranteed also to be cache line boundaries).
|
D | kmemcheck.txt | 132 any context, we need a temporary storage area which is guaranteed not
|
D | kprobes.txt | 150 is guaranteed to be called upon function return. If the entry_handler
|
D | DMA-API-HOWTO.txt | 412 guaranteed to be aligned to the smallest PAGE_SIZE order which
|
D | CodingStyle | 732 from void pointer to any other pointer type is guaranteed by the C programming
|
D | kernel-parameters.txt | 2840 every device is guaranteed to support. This
|
/linux-4.4.14/Documentation/filesystems/ |
D | jfs.txt | 23 guaranteed if the system abnormally abends.
|
D | ocfs2.txt | 98 therefore full cluster coherency is guaranteed even
|
D | directory-locking | 107 These operations are guaranteed to avoid loop creation. Indeed,
|
D | nilfs2.txt | 71 blocks. That means, it is guaranteed that no
|
D | fiemap.txt | 151 Extent offsets and length are not guaranteed to be block aligned.
|
D | Locking | 157 ->quota_read() and ->quota_write() functions are both guaranteed to 289 with lock on page, but that is not guaranteed. Considering the currently
|
D | porting | 442 local filesystems can ignore tha argument - they are guaranteed that the
|
D | ext2.txt | 358 in that transaction are guaranteed to represent a valid filesystem state,
|
D | relay.txt | 270 idea - you're guaranteed to either overwrite data or lose events
|
/linux-4.4.14/drivers/block/paride/ |
D | Transition-notes | 123 We don't need to reset it to NULL, since we are guaranteed that there 126 reason - the value is guaranteed to be set by the last ps_set_intr() and
|
/linux-4.4.14/arch/sh/ |
D | Kconfig.debug | 77 can already be guaranteed to ber zeroed on boot, say Y.
|
/linux-4.4.14/Documentation/x86/ |
D | tlb.txt | 46 guaranteed to flush a full 2MB [1], hugetlbfs always uses the full
|
D | boot.txt | 1022 uncompressed. No segments, except CS, are guaranteed to be
|
/linux-4.4.14/Documentation/ABI/ |
D | README | 16 them will be guaranteed for at least 2 years. Most interfaces
|
/linux-4.4.14/Documentation/RCU/ |
D | NMI-RCU.txt | 93 Since NMI handlers disable preemption, synchronize_sched() is guaranteed
|
D | rcubarrier.txt | 65 calls, but this is still not guaranteed to work. If there is a very 202 which point, all earlier RCU callbacks are guaranteed to have completed.
|
D | whatisRCU.txt | 142 accessed during an RCU read-side critical section is guaranteed to 608 called are guaranteed to have completed -- there is no way that 666 synchronize_rcu(). Once synchronize_rcu() returns, we are guaranteed
|
D | checklist.txt | 353 but are by -no- means guaranteed to be. For example, if a given
|
D | RTFP.txt | 24 of "quiescent states" in the VM/XA hypervisor that are guaranteed not
|
/linux-4.4.14/Documentation/tpm/ |
D | xen-tpmfront.txt | 20 separation guaranteed by the hypervisor. The vTPM domains are implemented in
|
/linux-4.4.14/Documentation/frv/ |
D | atomic-ops.txt | 47 task pointer in the kernel, and so is guaranteed to be non-zero).
|
/linux-4.4.14/Documentation/misc-devices/ |
D | lis3lv02d | 44 but interrupt behaviour is not guaranteed to work reliably. In test mode, the
|
/linux-4.4.14/drivers/media/pci/ttpci/ |
D | Kconfig | 44 on the video output. This is kind of nonstandard and not guaranteed to
|
/linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/ |
D | arm,gic.txt | 45 DEFINED and as such not guaranteed to be present (most SoC available
|
/linux-4.4.14/Documentation/ia64/ |
D | fsys.txt | 220 PSR.is Unchanged (guaranteed to be 0 on entry to the gate page). 222 PSR.it Unchanged (guaranteed to be 1).
|
/linux-4.4.14/Documentation/serial/ |
D | tty.txt | 101 processing. The number of bytes is guaranteed not 271 driver is guaranteed following up calls to
|
/linux-4.4.14/Documentation/vm/ |
D | transhuge.txt | 112 guaranteed, but it may be more likely in case the allocation is for a 300 To be guaranteed that the kernel will map a 2M page immediately in any 364 guaranteed by the time wait_split_huge_page returns, the pmd isn't
|
/linux-4.4.14/Documentation/arm/ |
D | kernel_mode_neon.txt | 53 they are guaranteed not to touch the NEON/VFP registers. For this reason, the
|
D | kernel_user_helpers.txt | 14 guaranteed to be stable.
|
/linux-4.4.14/Documentation/cgroups/ |
D | cgroups.txt | 234 is not guaranteed to be sorted. Writing a thread ID into this file 237 not guaranteed to be sorted or free of duplicate TGIDs, and userspace 586 @tset contains the tasks to be attached and is guaranteed to have at 590 - it's guaranteed that all are from the same thread group
|
/linux-4.4.14/arch/m68k/ifpsp060/ |
D | os.S | 64 | The addresses within the 060SP are guaranteed to be on the stack.
|
/linux-4.4.14/scripts/ |
D | spelling.txt | 459 gaurenteed||guaranteed 468 guarenteed||guaranteed
|
/linux-4.4.14/Documentation/driver-model/ |
D | devres.txt | 97 If a driver uses dmam_alloc_coherent(), the area is guaranteed to be
|
/linux-4.4.14/arch/m68k/fpsp040/ |
D | skeleton.S | 397 | The supervisor source address is guaranteed to point into the supervisor
|
/linux-4.4.14/Documentation/devicetree/bindings/bus/ |
D | mvebu-mbus.txt | 199 to be set by the operating system and that are guaranteed to be free of overlaps
|
/linux-4.4.14/Documentation/fb/ |
D | sstfb.txt | 6 video boards. It's highly experimental code, but is guaranteed to work
|
/linux-4.4.14/Documentation/powerpc/ |
D | transactional_memory.txt | 17 guaranteed to either complete atomically or roll back and undo any partial
|
D | hvcs.txt | 262 adapter is not guaranteed to remain the same across system reboots. Look
|
/linux-4.4.14/Documentation/devicetree/bindings/arm/ |
D | idle-states.txt | 80 exit-latency may be guaranteed only after entry-latency has passed. 286 The exit-latency-us duration may be guaranteed
|
D | topology.txt | 94 levels) since name uniqueness will be guaranteed by the device tree hierarchy.
|
/linux-4.4.14/Documentation/usb/ |
D | persist.txt | 138 aren't guaranteed to be 100% accurate.
|
D | power-management.txt | 440 method, at which time the device is guaranteed not to be
|
/linux-4.4.14/mm/ |
D | Kconfig | 418 memory footprint of applications without a guaranteed 427 memory footprint of applications without a guaranteed
|
/linux-4.4.14/Documentation/ioctl/ |
D | botching-up-ioctls.txt | 53 pain. And since getting things wrong on the first attempt is guaranteed you
|
/linux-4.4.14/Documentation/isdn/ |
D | README.sc | 4 guaranteed to fail. If you have a DataCommute/PRI installed in the test
|
/linux-4.4.14/Documentation/nfc/ |
D | nfc-hci.txt | 218 The wait is not interruptible because it is guaranteed that the command will
|
/linux-4.4.14/drivers/net/ethernet/intel/i40evf/ |
D | i40e_adminq_cmd.h | 670 __le16 guaranteed; member
|
/linux-4.4.14/Documentation/video4linux/ |
D | videobuf | 292 time, an operation which is not always guaranteed to work. Some drivers
|
/linux-4.4.14/drivers/net/ethernet/intel/i40e/ |
D | i40e_adminq_cmd.h | 673 __le16 guaranteed; member
|
/linux-4.4.14/Documentation/scsi/ |
D | aic79xx.txt | 93 This is guaranteed not to happen in Linux.
|
/linux-4.4.14/Documentation/trace/ |
D | events.txt | 256 fields can be guaranteed to propagate successfully to all events.
|
/linux-4.4.14/arch/s390/ |
D | Kconfig | 446 Fair distribution of the CPUs is not guaranteed.
|
/linux-4.4.14/Documentation/security/ |
D | credentials.txt | 491 This function is guaranteed to return 0, so that it can be tail-called at the
|
/linux-4.4.14/Documentation/PCI/ |
D | pci.txt | 404 2) MSI avoids DMA/IRQ race conditions. DMA to host memory is guaranteed
|
/linux-4.4.14/Documentation/netlabel/ |
D | draft-ietf-cipso-ipsecurity-01.txt | 154 be guaranteed if CIPSO is not the first IP option.
|
/linux-4.4.14/Documentation/scheduler/ |
D | sched-deadline.txt | 419 and that -deadline tasks will receive their runtime with a guaranteed
|
/linux-4.4.14/Documentation/sysctl/ |
D | kernel.txt | 235 process is not guaranteed access to /proc/<crashing pid>/). This
|
/linux-4.4.14/scripts/dtc/ |
D | dtc-lexer.lex.c_shipped | 1417 /* don't do the read, it's not guaranteed to return an EOF,
|
/linux-4.4.14/scripts/genksyms/ |
D | lex.lex.c_shipped | 1084 /* don't do the read, it's not guaranteed to return an EOF,
|
/linux-4.4.14/scripts/kconfig/ |
D | zconf.lex.c_shipped | 1564 /* don't do the read, it's not guaranteed to return an EOF,
|
/linux-4.4.14/Documentation/power/ |
D | devices.txt | 453 the suspend was carried out, but that can't be guaranteed (in fact, it usually
|
/linux-4.4.14/Documentation/locking/ |
D | rt-mutex-design.txt | 513 but never give up the wait_lock. So the PI chain loop is guaranteed to
|
/linux-4.4.14/drivers/mfd/ |
D | Kconfig | 135 response time cannot be guaranteed, we support ignoring
|
/linux-4.4.14/Documentation/block/ |
D | biodoc.txt | 591 subsystems like bio to maintain their own reserve memory pools for guaranteed
|