| /Documentation/admin-guide/cifs/ |
| D | authors.rst | 10 The author wishes to express his appreciation and thanks to:
12 improvements. Thanks to IBM for allowing me time and test resources to pursue
13 this project, to Jim McDonough from IBM (and the Samba Team) for his help, to
16 side of the original CIFS Unix extensions and reviewing and implementing
21 Newbigin and others for their work on the Linux smbfs module. Thanks to
23 Workgroup for their work specifying this highly complex protocol and finally
24 thanks to the Samba team for their technical advice and encouragement.
39 - Vince Negri and Dave Stahl (for finding an important caching bug)
44 - Shaggy (Dave Kleikamp) for innumerable small fs suggestions and some good cleanup
45 - Gunter Kukkukk (testing and suggestions for support of old servers)
[all …]
|
| D | todo.rst | 12 is a partial list of the known problems and missing features:
14 a) SMB3 (and SMB3.1.1) missing optional features:
18 - T10 copy offload ie "ODX" (copy chunk, and "Duplicate Extents" ioctl
21 b) improved sparse file support (fiemap and SEEK_HOLE are implemented
31 open/query/close and open/setinfo/close) to reduce the number of
32 roundtrips to the server and improve performance. Various cases
36 handle caching leases) and better using reference counters on file
39 f) Finish inotify support so kde and gnome file list windows
43 g) Add GUI tool to configure /proc/fs/cifs settings and for display of
46 h) implement support for security and trusted categories of xattrs
[all …]
|
| /Documentation/timers/ |
| D | hrtimers.rst | 9 back and forth trying to integrate high-resolution and high-precision
10 features into the existing timer framework, and after testing various
14 to solve this'), and spent a considerable effort trying to integrate
18 - the forced handling of low-resolution and high-resolution timers in
19 the same way leads to a lot of compromises, macro magic and #ifdef
20 mess. The timers.c code is very "tightly coded" around jiffies and
21 32-bitness assumptions, and has been honed and micro-optimized for a
23 for many years - and thus even small extensions to it easily break
25 code is very good and tight code, there's zero problems with it in its
45 error conditions in various I/O paths, such as networking and block
[all …]
|
| D | highres.rst | 2 High resolution timers and dynamic ticks design notes
6 and beyond". The paper is part of the OLS 2006 Proceedings Volume 1, which can
15 design of the Linux time(r) system before hrtimers and other building blocks
18 Note: the paper and the slides are talking about "clock event source", while we
24 - timeofday and clock source management
44 timeofday and clock source management
51 sources, which are registered in the framework and selected on a quality based
52 decision. The low level code provides hardware setup and readout routines and
63 The paper "We Are Not Getting Any Younger: A New Approach to Time and
75 period defined at compile time. The setup and selection of the event device
[all …]
|
| /Documentation/usb/ |
| D | CREDITS | 31 Linux USB driver effort and writing much of the larger uusbd driver.
35 and offering suggestions and sharing implementation experiences.
37 Additional thanks to the following companies and people for donations
38 of hardware, support, time and development (this is from the original
44 - 3Com GmbH for donating a ISDN Pro TA and supporting me
45 in technical questions and with test equipment. I'd never
52 Operating System and supports this project with
74 protocol. They've also donated a F-23 digital joystick and a
79 leading manufacturer for active and passive ISDN Controllers
80 and CAPI 2.0-based software. The active design of the AVM B1
[all …]
|
| /Documentation/fb/ |
| D | api.rst | 12 with frame buffer devices. In-kernel APIs between device drivers and the frame
16 behaviours differ in subtle (and not so subtle) ways. This document describes
24 Device and driver capabilities are reported in the fixed screen information
34 expect from the device and driver.
43 2. Types and visuals
50 Formats are described by frame buffer types and visuals. Some visuals require
52 bits_per_pixel, grayscale, red, green, blue and transp fields.
54 Visuals describe how color information is encoded and assembled to create
56 types and visuals are supported.
64 Padding at end of lines may be present and is then reported through the fixed
[all …]
|
| /Documentation/process/ |
| D | code-of-conduct-interpretation.rst | 8 open-source community is unique and the Linux kernel is no exception.
11 to be static over time, and will adjust it as needed.
14 to "traditional" ways of developing software. Your contributions and
16 critique and criticism. The review will almost always require
21 system kernel ever, and we do not want to do anything to cause the
22 quality of submission and eventual result to ever decrease.
29 subsystem, driver, or file, and is listed in the MAINTAINERS file in the
35 The Code of Conduct mentions rights and responsibilities for
36 maintainers, and this needs some further clarifications.
38 First and foremost, it is a reasonable expectation to have maintainers
[all …]
|
| D | code-of-conduct.rst | 9 In the interest of fostering an open and welcoming environment, we as
10 contributors and maintainers pledge to making participation in our project and
12 size, disability, ethnicity, sex characteristics, gender identity and
14 personal appearance, race, religion, or sexual identity and orientation.
22 * Using welcoming and inclusive language
23 * Being respectful of differing viewpoints and experiences
31 * The use of sexualized language or imagery and unwelcome sexual attention or
33 * Trolling, insulting/derogatory comments, and personal or political attacks
45 and are expected to take appropriate and fair corrective action in response to
48 Maintainers have the right and responsibility to remove, edit, or reject
[all …]
|
| /Documentation/core-api/ |
| D | workqueue.rst | 14 is needed and the workqueue (wq) API is the most commonly used
20 queue is called workqueue and the thread is called worker.
32 worker thread per CPU and a single threaded (ST) wq had one worker
35 wq users over the years and with the number of CPU cores continuously
40 provided was unsatisfactory. The limitation was common to both ST and
47 The tension between the provided level of concurrency and resource
49 choosing to use ST wq for polling PIOs and accepting an unnecessary
64 * Automatically regulate worker pool and level of concurrency so that
77 item pointing to that function and queue that work item on a
86 subsystems and drivers queue work items on and the backend mechanism
[all …]
|
| /Documentation/hwmon/ |
| D | xdpe12284.rst | 25 The family includes XDPE12284 and XDPE12254 devices.
28 - Intel VR13 and VR13HC rev 1.3, IMVP8 rev 1.2 and IMPVP9 rev 1.3 DC-DC
33 Devices support linear format for reading input voltage, input and output current,
34 input and output power and temperature.
44 The driver provides for current: input, maximum and critical thresholds
45 and maximum and critical alarms. Critical thresholds and critical alarm are
48 indexes 1, 2 are for "iin" and 3, 4 for "iout":
62 The driver provides for voltage: input, critical and low critical thresholds
63 and critical and low critical alarms.
65 indexes 1, 2 are for "vin" and 3, 4 for "vout":
[all …]
|
| /Documentation/x86/ |
| D | intel_txt.rst | 15 - Measurement and verification of launched environment
17 Intel TXT is part of the vPro(TM) brand and is also available some
19 based on the Q35, X38, Q45, and Q43 Express chipsets (e.g. Dell
20 Optiplex 755, HP dc7800, etc.) and mobile systems based on the GM45,
21 PM45, and GS45 Express chipsets.
47 uses Intel TXT to perform a measured and verified launch of an OS
55 w/ TXT support since v3.2), and now Linux kernels.
61 While there are many products and technologies that attempt to
64 Measurement Architecture (IMA) and Linux Integrity Module interface
69 starting at system reset and requires measurement of all code
[all …]
|
| /Documentation/vm/ |
| D | frontswap.rst | 11 (Note, frontswap -- and :ref:`cleancache` (merged at 3.0) -- are the "frontends"
12 and the only necessary changes to the core kernel for transcendent memory;
15 for a detailed overview of frontswap and related kernel parts)
25 kernel and is of unknown and possibly time-varying size. The driver
27 frontswap_ops funcs appropriately and the functions it provides must
32 copy the page to transcendent memory and associate it with the type and
36 from transcendent memory and an "invalidate_area" will remove ALL pages
37 associated with the swap type (e.g., like swapoff) and notify the "device"
43 success, the data has been successfully saved to transcendent memory and
44 a disk write and, if the data is later read back, a disk read are avoided.
[all …]
|
| D | cleancache.rst | 19 that is not directly accessible or addressable by the kernel and is
20 of unknown and possibly time-varying size.
25 and a disk access is avoided.
28 in Xen (using hypervisor memory) and zcache (using in-kernel compressed
29 memory) and other implementations are in development.
43 by the kernel and so may or may not still be in cleancache at any later time.
45 Cleancache has complete discretion over what pages to preserve and what
46 pages to discard and when.
51 (presumably about-to-be-evicted) page into cleancache and associate it with
52 the pool id, a file key, and a page index into the file. (The combination
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | v4l2.rst | 39 Revision and Copyright
50 - Documented libv4l, designed and added v4l2grab example, Remote Controller chapter.
54 - Original author of the V4L2 API and documentation.
63 - Original author of the V4L2 API and documentation.
76 - Designed and documented the multi-planar API.
84 - Introduce HSV formats and other minor changes.
88 - Designed and documented the VIDIOC_ENUM_FRAMESIZES and VIDIOC_ENUM_FRAMEINTERVALS ioctls.
96 …ned and documented the VIDIOC_LOG_STATUS ioctl, the extended control ioctls, major parts of the sl…
101 part can be used and distributed without restrictions.
115 ctrl_class and which. Which is used to select the current value of the
[all …]
|
| D | hist-v4l2.rst | 12 and began to work on documentation, example drivers and applications.
15 another four years and two stable kernel releases until the new API was
28 meaningless ``O_TRUNC`` :c:func:`open()` flag, and the
29 aliases ``O_NONCAP`` and ``O_NOIO`` were defined. Applications can set
32 identifiers are now ordinals instead of flags, and the
33 ``video_std_construct()`` helper function takes id and
40 struct ``video_standard`` and the color subcarrier fields were
53 and ``V4L2_PIX_FMT_RGB32`` changed to ``V4L2_PIX_FMT_BGR32``. Audio
55 :ref:`VIDIOC_G_CTRL <VIDIOC_G_CTRL>` and
59 module. The ``YUV422`` and ``YUV411`` planar image formats were added.
[all …]
|
| /Documentation/ABI/testing/ |
| D | debugfs-hisi-sec | 7 Only available for PF, and take no other effect on SEC.
12 Description: One SEC controller has one PF and multiple VFs, each function
21 Available for PF and VF in host. VF in guest currently only
37 Only available for PF, and take no other effect on SEC.
44 Available for both PF and VF, and take no other effect on SEC.
50 Available for both PF and VF, and take no other effect on SEC.
56 Available for both PF and VF, and take no other effect on SEC.
62 Available for both PF and VF, and take no other effect on SEC.
68 Available for both PF and VF, and take no other effect on SEC.
74 Four states: initiated, started, stopped and closed.
[all …]
|
| /Documentation/scsi/ |
| D | FlashPoint.rst | 21 drivers and information will be available on October 15th at
26 development and provided technical support for our host adapters for several
27 years, and are pleased to now make our FlashPoint products available to this
34 SPARC, SGI MIPS, Motorola 68k, Digital Alpha AXP and Motorola PowerPC
36 System, Emacs, and TCP/IP networking. Further information is available at
37 http://www.linux.org and http://www.ssc.com/.
43 and file server environments, are available in narrow, wide, dual channel,
44 and dual channel wide versions. These adapters feature SeqEngine
45 automation technology, which minimizes SCSI command overhead and reduces
52 producer of RAID technology and network management products. The company
[all …]
|
| D | ChangeLog.lpfc | 12 for fabric and nport logins out of lpfc_cmpl_els_flogi.
18 PRLI...) are errored back and scan() terminates.
28 find command in both TX and TX completion queues. Return ERROR
62 - kill struct lpfc_scsi_dma_buf and embedded the two members
67 ever used by the driver, just reported to userspace (and that in
72 32bit and 64bit defines on some archs.
82 * Revise TRANSPORT_PATCHES_V2 so that lpfc_target is removed and
84 * Changed RW attributes of scan_down, max_luns and fcp_bind_method
88 list and marked for ADISC.
102 * Use DMA_64BIT_MASK and DMA_32BIT_MASK defines instead of
[all …]
|
| /Documentation/admin-guide/ |
| D | perf-security.rst | 3 Perf events and tool security
12 direct usage of perf_events system call API [2]_ and over data files
15 units (PMU) [2]_ and Perf collect and expose for performance analysis.
16 Collected system and performance data may be split into several
19 1. System hardware and software configuration data, for example: a CPU
20 model and its cache configuration, an amount of available memory and
21 its topology, used kernel and Perf versions, performance monitoring
25 2. User and kernel module paths and their load addresses with sizes,
26 process and thread names with their PIDs and TIDs, timestamps for
27 captured hardware and software events.
[all …]
|
| /Documentation/w1/masters/ |
| D | ds2490.rst | 19 which has 0x81 family ID integrated chip and DS2490
22 Notes and limitations.
24 - The weak pullup current is a minimum of 0.9mA and maximum of 6.0mA.
25 - The 5V strong pullup is supported with a minimum of 5.9mA and a
33 a write buffer and a read buffer (along with sizes) as arguments.
35 buffer, and strong pullup all in one command, instead of the current
36 1 reset bus, 2 write the match rom command and slave rom id, 3 block
37 write and read data. The write buffer needs to have the match rom
38 command and slave rom id prepended to the front of the requested
40 - The hardware supports normal, flexible, and overdrive bus
[all …]
|
| /Documentation/admin-guide/media/ |
| D | davinci-vpbe.rst | 13 Implements creation of video2 and video3 device nodes and
14 provides v4l2 device interface to manage VID0 and VID1 layers.
18 Loads up VENC, OSD and external encoders such as ths8200. It provides
23 controller port is done at init time based on default output and standard
28 for setting up the interface between VENC and external encoders based on
33 patch series, the interconnection and enabling and setting of the external
34 encoders is not present, and would be a part of the next patch series.
38 Responsible for setting outputs provided through internal DACs and also
42 the board specific table and the values are used to set the timings in
47 timings for the resolution supported and setting the dot clock. So we could
[all …]
|
| /Documentation/networking/ |
| D | af_xdp.rst | 13 This document assumes that the reader is familiar with BPF and XDP. If
24 syscall. Associated with each XSK are two rings: the RX ring and the
25 TX ring. A socket can receive packets on the RX ring and it can send
26 packets on the TX ring. These rings are registered and sized with the
27 setsockopts XDP_RX_RING and XDP_TX_RING, respectively. It is mandatory
30 UMEM. RX and TX can share the same UMEM so that a packet does not have
31 to be copied between RX and TX. Moreover, if a packet needs to be kept
33 to that packet can be changed to point to another and reused right
42 UMEM also has two rings: the FILL ring and the COMPLETION ring. The
47 kernel has transmitted completely and can now be used again by user
[all …]
|
| /Documentation/sound/soc/ |
| D | overview.rst | 7 pxa2xx, au1x00, iMX, etc) and portable audio codecs. Prior to the ASoC
12 CPU. This is not ideal and leads to code duplication - for example,
17 event). These are quite common events on portable devices and often require
30 The ASoC layer is designed to address these issues and provide the following
34 and machines.
36 * Easy I2S/PCM audio interface setup between codec and SoC. Each SoC
37 interface and codec registers its audio interface capabilities with the
38 core and are subsequently matched and configured when the application
43 internal power blocks depending on the internal codec audio routing and any
46 * Pop and click reduction. Pops and clicks can be reduced by powering the
[all …]
|
| /Documentation/networking/device_drivers/ethernet/marvell/ |
| D | octeontx2.rst | 20 resources from the network, crypto and other functional blocks into
21 PCI-compatible physical and virtual functions. Each functional block
23 RVU supports multiple PCIe SRIOV physical functions (PFs) and virtual
25 and has privileges to provision RVU functional block's LFs to each of the
39 Used for both networking and non networking usecases
51 - Also assigns MSIX vectors to each of PF and VFs.
57 Linux kernel will have multiple drivers registering to different PF and VFs
64 supports resource provisioning and configuration of functional blocks.
66 funcionality is achieved via configuration requests from PFs and VFs.
69 receiving requests AF does resource provisioning and other HW configuration.
[all …]
|
| /Documentation/networking/device_drivers/cable/ |
| D | sb1000.rst | 24 to configure the cable modem and network interface (usually called "cm0");
62 and to say "M" to the sb1000 driver. Also say "Y" or "M" to all the standard
63 networking questions to get TCP/IP and PPP networking support.
70 3. Build and install the kernel and modules as usual.
75 of "pnpdump" to a file and editing this file to set the correct I/O ports,
76 IRQ, and DMA settings for all your PnP cards. Make sure none of the settings
79 errors and fix as necessary. (As an aside, I use I/O ports 0x110 and
80 0x310 and IRQ 11 for my SB1000 card and these work well for me. YMMV.)
86 and do a ``make cmconfig`` and then ``install -c cmconfig /usr/local/sbin``.
88 and ready for installation, not just cmconfig.
[all …]
|