Searched full:share (Results 1 – 25 of 296) sorted by relevance
12345678910>>...12
| /Documentation/misc-devices/ |
| D | uacce.rst | 9 This differs from the data sharing between cpu and io device, which share
12 share the same virtual address in the communication.
14 IOMMU share the same CPU page tables and as a result the same translation
97 hardware by ioctl (as control path) or share memory (as data path).
109 * @UACCE_QFRT_DUS: device user share region
123 The device user share region is used for share data buffer between user process
|
| /Documentation/filesystems/smb/ |
| D | cifsroot.rst | 57 cifsroot=//<server-ip>/<share>[,options]
60 located in the <server-ip> and <share> specified in this option.
67 share
68 Path to SMB share (rootfs).
76 Export root file system as a Samba share in smb.conf file::
|
| D | ksmbd.rst | 57 requests (dcerpc and share/user info). It handles RPC calls (at a minimum few
113 support are Leases, Notify, ACLs and Share modes.
134 2. Create /usr/local/etc/ksmbd/ksmbd.conf file, add SMB share in ksmbd.conf file.
141 3. Create user/password for SMB share.
146 $ sudo ksmbd.adduser -a <Enter USERNAME for SMB share access>
161 6. Access share from Windows or Linux using SMB3 client (cifs.ko or smbclient of samba)
|
| /Documentation/arch/mips/ |
| D | ingenic-tcu.rst | 41 - Each channel can generate an interrupt. Some channels share an interrupt
45 own interrupt line; channels 2-7 share the last interrupt line.
46 - On JZ4725B, channel 0 has its own interrupt; channels 1-5 share one
49 channels 0-4 and (if eight channels) 6-7 all share one interrupt line;
|
| /Documentation/admin-guide/hw-vuln/ |
| D | core-scheduling.rst | 7 share a core. These groups can be specified either for security usecases (one
11 do share hardware resource needs). This document only describes the security
21 user-designated trusted group can share a core. This increase in core sharing
79 The simplest way to build hierarchies of threads/processes which share a
89 specified task or a share a cookie with a task. In combination this allows a
91 scheduling group and share it with already running tasks.
97 each other and share a core.
207 allowing system processes (trusted tasks) to share a core.
|
| /Documentation/devicetree/bindings/sound/ |
| D | mediatek,mt8188-afe.yaml | 100 etdm modules can share the same external clock pin. Specify
110 etdm modules can share the same external clock pin. Specify
120 etdm modules can share the same external clock pin. Specify
130 etdm modules can share the same external clock pin. Specify
|
| D | max98373.txt | 26 to share a single data output channel on alternating frames.
|
| /Documentation/devicetree/bindings/net/can/ |
| D | st,stm32-bxcan.yaml | 25 two CAN peripherals in dual CAN configuration. In that case they share
36 share some of the required logic.
|
| /Documentation/kbuild/ |
| D | Kconfig.recursion-issue-02 | 11 # drivers if they share a common core requirement and use disjoint semantics to
13 # use "select". For instance it means if a driver A and driver B share the same
|
| /Documentation/block/ |
| D | bfq-iosched.rst | 5 BFQ is a proportional-share I/O scheduler, with some extra
158 BFQ is a proportional-share I/O scheduler, whose general structure,
214 applications more than their fair share of the device
254 - First, with any proportional-share scheduler, the maximum
400 receives its allotted share of the bandwidth. The first condition is
452 increases the bandwidth share of privileged applications, as the main
500 share. To activate cgroups support, set BFQ_GROUP_IOSCHED.
505 With BFQ, proportional share means true proportional share of the
512 group, the children of the group share the whole bandwidth of the
515 same share of the whole group bandwidth, unless the ioprio of the
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-amd-pmc | 13 APU/CPU models that can share the same firmware binary.
|
| /Documentation/admin-guide/cifs/ |
| D | usage.rst | 97 2) an entry for the share in /etc/fstab indicating that a user may
132 to the file /etc/fstab for each //server/share you wish to mount, but
188 outside of the share, so in Samba versions prior to 3.0.6, most symlinks to
195 files that are outside of the share) to a samba specific format on the server
232 syntax) instead of the more widely used UNC format (i.e. \\server\share)::
392 mount the network share read-write (note that the
393 server may still consider the share read-only)
395 mount network share read-only
470 single share (since inode numbers on the servers might not
494 reloaded (or the user remounts the share).
[all …]
|
| /Documentation/devicetree/bindings/cpufreq/ |
| D | cpufreq-spear.txt | 6 which share clock across all CPUs.
|
| D | cpufreq-dt.txt | 4 both uniprocessor (UP) and symmetric multiprocessor (SMP) systems which share
|
| /Documentation/devicetree/bindings/clock/ |
| D | marvell,berlin.txt | 9 (BG2, BG2CD, BG2Q) SoCs share the same IP for PLLs and clocks, with some
|
| /Documentation/devicetree/bindings/iio/humidity/ |
| D | st,hts221.yaml | 27 is useful if several sensors share the same interrupt line.
|
| /Documentation/sound/cards/ |
| D | mixart.rst | 98 The firmware binaries are installed on /usr/share/alsa/firmware
99 (or /usr/local/share/alsa/firmware, depending to the prefix option of
|
| /Documentation/userspace-api/media/v4l/ |
| D | app-pri.rst | 9 When multiple applications share a device it may be desirable to assign
|
| /Documentation/admin-guide/mm/ |
| D | numaperf.rst | 9 node. These disparate memory ranges may share some characteristics, such
15 characteristics. Some memory may share the same node as a CPU, and others
56 nodes' access characteristics share the same performance relative to other
|
| /Documentation/devicetree/bindings/iio/temperature/ |
| D | adi,ltc2983.yaml | 231 adi,rsense-share:
283 adi,current-rotate: [ "adi,rsense-share" ]
322 adi,rsense-share:
367 adi,current-rotate: [ "adi,rsense-share" ]
522 adi,rsense-share;
|
| /Documentation/arch/x86/ |
| D | sva.rst | 105 process share the same page tables, thus the same MSR value.
115 other devices will share the same PASID.
159 * Many threads within a process can share a single portal to access
162 which case they still share one device hardware workqueue.
173 work in the same address space, i.e., to share it. Some call it Shared
|
| /Documentation/devicetree/bindings/net/ |
| D | fsl,enetc-mdio.yaml | 12 provides a means for different software modules to share a single set of MDIO
|
| /Documentation/tee/ |
| D | ts-tee.rst | 26 The generic TEE design is to share memory at once with the Trusted OS, which can
30 share memory with each SP based on its endpoint ID; therefore a separate TEE
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | st,spear3xx-shirq.txt | 9 may share same set of status/mask registers spanning across different
|
| /Documentation/driver-api/ |
| D | miscellaneous.rst | 10 .. kernel-doc:: drivers/parport/share.c
|
12345678910>>...12