Searched full:ll (Results 1 – 25 of 195) sorted by relevance
12345678
| /Documentation/ |
| D | atomic_t.txt | 116 will invalidate a LL/SC or fail a CMPXCHG.
152 are time critical and can, (typically) on LL/SC architectures, be more
265 t = LL.acq *y (0)
326 indefinitely. However, this is not evident on LL/SC architectures, because
327 while an LL/SC architecture 'can/should/must' provide forward progress
328 guarantees between competing LL/SC sections, such a guarantee does not
329 transfer to cmpxchg() implemented using LL/SC. Consider:
336 which on LL/SC becomes something like:
342 volatile asm ("1: LL %[oldval], %[v]\n"
356 However, even the forward branch from the failed compare can cause the LL/SC
|
| /Documentation/driver-api/media/drivers/ |
| D | tuners.rst | 31 L= Secam LL
34 Q= BG+I+DK+LL
69 MF: BG LL w/ Secam (Multi France)
70 ME: BG DK I LL (Multi Europe)
88 xx1x: Pal DK, Secam LL
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | devices.rst | 52 task to a new cgroup. (Again we'll probably want to change that).
65 more access than the cgroup's parent, it'll be removed from the whitelist.
81 it'll propagate down and after revalidating B's entries, the whitelist entry
89 anymore, they'll be deleted.
111 but now it'll be possible to add new entries to B::
|
| /Documentation/admin-guide/device-mapper/ |
| D | zero.rst | 21 desired size of the sparse device. For this example, we'll assume a 10TB
29 space available to the sparse device. For this example, we'll assume /dev/sdb1
|
| D | snapshot.rst | 108 we'll have this situation (with volumes in above order)::
117 # ls -lL /dev/mapper/volumeGroup-*
138 we'll now have this situation::
146 # ls -lL /dev/mapper/volumeGroup-*
|
| /Documentation/filesystems/bcachefs/ |
| D | CodingStyle.rst | 53 the compiler could check. This is something that exists today, but it'll likely
112 a user waiting. They'll thank you in the long run, and when they understand
113 what you're doing you'll be amazed at how patient they're happy to be. Users
126 time you spend at it the better you'll get, and you the developer are the
135 Nobody writes all perfect code that all gets shipped, and you'll be much more
160 often go astray - doing something because it seems like it'll be useful often
|
| /Documentation/admin-guide/ |
| D | iostats.rst | 15 the information. Throughout this document we'll assume that sysfs
43 you'll avoid the overhead of 50, 100, or 500 or more opens/closes with
48 By contrast, in 2.6+ if you look at ``/sys/block/hda/stat``, you'll
63 system-wide stats you'll have to find all the devices and sum them all up.
157 in 2.4. Consequently, you'll see a different statistics output on 2.6+ for
199 Linux hasn't added it already, here's the line you'll want to add to
|
| /Documentation/process/ |
| D | management-style.rst | 15 might not actually be true. You'll have to decide for yourself.
125 clear which approach is better, they'll eventually figure it out. The
139 Most people are idiots, and being a manager means you'll have to deal
197 easier. In particular, they'll be able to make your decisions for you,
223 best way of taking the blame: do it for someone else. You'll feel good
224 for taking the fall, they'll feel good about not getting blamed, and the
238 you've followed the previous rules, you'll be pretty good at saying that
272 a while, and you'll feel cleansed. Just don't crap too close to home.
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-arb-gpio-challenge.yaml | 30 others can see. These are all active low with pull-ups enabled. We'll
78 We'll give up after this many microseconds.
83 We'll attempt another claim after this many microseconds.
|
| /Documentation/networking/ |
| D | tproxy.rst | 36 Because of certain restrictions in the IPv4 routing output code you'll have to
76 Note that for this to work you'll have to modify the proxy to enable (SOL_IP,
87 To use tproxy you'll need to have the following modules compiled for iptables:
|
| D | packet_mmap.rst | 647 struct sockaddr_ll ll;
664 memset(&ll, 0, sizeof(ll));
665 ll.sll_family = AF_PACKET;
666 ll.sll_ifindex = ifr.ifr_ifindex;
667 err = bind(fd, (struct sockaddr *) &ll, sizeof(ll));
829 struct sockaddr_ll ll;
874 memset(&ll, 0, sizeof(ll));
875 ll.sll_family = PF_PACKET;
876 ll.sll_protocol = htons(ETH_P_ALL);
877 ll.sll_ifindex = if_nametoindex(netdev);
[all …]
|
| /Documentation/hwmon/ |
| D | adm1025.rst | 52 properly, you'll have a wrong +12V reading or a wrong VID reading. The way
55 out not to be true in some cases, we'll provide a module parameter to force
|
| /Documentation/arch/riscv/ |
| D | patch-acceptance.rst | 39 We'll only accept patches for new modules or extensions if the
52 RISC-V extensions, we'll only consider patches for extensions that either:
|
| /Documentation/devicetree/bindings/memory-controllers/ti/ |
| D | emif.txt | 53 - hw-caps-ll-interface : Have this property if the controller
68 hw-caps-ll-interface;
|
| /Documentation/sphinx/ |
| D | kernellog.py | 7 # We don't support 1.4 anymore, but we'll keep the wrappers around until
|
| /Documentation/input/joydev/ |
| D | joystick.rst | 63 For all joystick drivers to function, you'll need the userland interface
68 For gameport joysticks, you'll have to load the gameport driver as well::
72 And for serial port joysticks, you'll need the serial input line
78 In addition to that, you'll need the joystick driver module itself, most
79 usually you'll have an analog joystick::
162 you'll need to specify the types either on the kernel command line or on the
243 rear side of the joystick. However, moving it, you'll reset the joystick,
310 allow connecting analog joysticks to them, you'll need to load the analog
581 :A: Yes, it is possible, but it'll burn your serial port or the pad. It
|
| /Documentation/bpf/ |
| D | llvm_reloc.rst | 34 0: 18 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 r1 = 0 ll
37 3: 18 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 r2 = 0 ll
41 7: 18 01 00 00 08 00 00 00 00 00 00 00 00 00 00 00 r1 = 8 ll
45 11: 18 01 00 00 0c 00 00 00 00 00 00 00 00 00 00 00 r1 = 12 ll
176 8: 18 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 r1 = 0 ll
522 23: r1 = 0x2 ll
525 26: r1 = 0x2 ll
540 30: r1 = 0x1 ll
543 33: r1 = 0x1 ll
|
| /Documentation/arch/x86/x86_64/ |
| D | fake-numa-for-cpusets.rst | 23 For the purposes of this introduction, we'll assume a very primitive NUMA
27 you'll determine a better setup to minimize the number of nodes you have to deal
|
| /Documentation/admin-guide/media/ |
| D | dvb_references.rst | 17 There, you'll find lots of information, from both development and usage
|
| /Documentation/ABI/testing/ |
| D | sysfs-devices-state_synced | 15 run before the kernel starts), then it'll keep those resources
|
| D | dell-smbios-wmi | 12 1) To perform an SMBIOS call from userspace, you'll need to
|
| /Documentation/arch/arm/ |
| D | porting.rst | 78 basis by the kernel. I'll call this the user segment.
80 Anything above TASK_SIZE is common to all processes. I'll call
|
| /Documentation/arch/powerpc/ |
| D | mpc52xx.rst | 42 mention you/your company in the copyright of some code, I'll correct it
|
| /Documentation/i2c/busses/ |
| D | i2c-taos-evm.rst | 25 In order to use this driver, you'll need the serport driver, and the
|
| /Documentation/filesystems/ |
| D | dlmfs.rst | 51 You'll want to start heartbeating on a volume which all the nodes in
99 operation. If the lock succeeds, you'll get an fd.
|
12345678