Searched full:work (Results 1 – 25 of 948) sorted by relevance
12345678910>>...38
| /Documentation/core-api/ |
| D | workqueue.rst | 17 When such an asynchronous execution context is needed, a work item
22 While there are work items on the workqueue the worker executes the
23 functions associated with the work items one after the other. When
24 there is no work item left on the workqueue the worker becomes idle.
25 When a new work item gets queued, the worker begins executing again.
43 while an ST wq one for the whole system. Work items had to compete for
72 abstraction, the work item, is introduced.
74 A work item is a simple struct that holds a pointer to the function
76 wants a function to be executed asynchronously it has to set up a work
77 item pointing to that function and queue that work item on a
[all …]
|
| /Documentation/admin-guide/cifs/ |
| D | authors.rst | 15 Jeremy Allison of the Samba team has done invaluable work in adding the server
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
36 - Mark Hamzy (for some of the early cifs IPv6 work)
47 - Jeff Layton (many, many fixes, as well as great work on the cifs Kerberos code)
49 - Pavel Shilovsky (for great work adding SMB2 support, and various SMB3 features)
50 - Aurelien Aptel (for DFS SMB3 work and some key bug fixes)
51 - Ronnie Sahlberg (for SMB3 xattr work, bug fixes, and lots of great work on compounding)
54 - Paulo Alcantara (for some excellent work in DFS, and in booting from SMB3)
55 - Long Li (some great work on RDMA, SMB Direct)
|
| /Documentation/driver-api/media/drivers/ |
| D | contributors.rst | 19 - for his work on the initial Linux DVB driver
24 - for their continuing work on the DVB driver
42 - for various fixes regarding tuning, OSD and CI stuff and his work on VDR
61 their work on the dbox2 port of the DVB driver
79 - for all the work for the FlexCopII chipset by B2C2,Inc.
83 - for his work on the budget drivers, the demux code,
88 - for his work on calculating and checking the crc's for the
|
| D | bttv-devel.rst | 10 Making video work often is not a big deal, because this is handled
16 Sound will work only, if the correct entry is used (for video it often
29 card, you can check if one of the existing entries does work for you
35 module like ``msp3400`` to make sound work. If there isn't one for the
47 Still doesn't work? Looks like some driver hacking is required.
|
| /Documentation/ABI/stable/ |
| D | sysfs-driver-dma-idxd | 24 Description: The largest number of work descriptors in a batch.
31 Description: The maximum work queue size supported by this device.
68 Description: The maximum work queue number that this device supports.
113 Description: The assigned work queue under this device.
159 Description: To indicate block on fault is allowed or not for the work queue
166 Description: The group id that this work queue belongs to.
172 Description: The work queue size for this work queue.
178 Description: The type of this work queue, it can be "kernel" type for work
179 queue usages in the kernel space or "user" type for work queue
186 Description: The minor number assigned to this work queue by the character
[all …]
|
| /Documentation/admin-guide/media/ |
| D | cafe_ccic.rst | 18 QVGA modes work; CIF is there but the colors remain funky. Only the OV7670
19 sensor is known to work with this controller at this time.
21 To try it out: either of these commands will work:
49 systems, however, it will work well with only two.
52 will consent to work with. Default is one, but, on slower systems,
|
| /Documentation/process/ |
| D | 6.Followthrough.rst | 9 developers can make is to conclude that their work is now done. In truth,
11 with, possibly, quite a bit of work yet to be done.
16 code. You, as the author of that code, will be expected to work with the
39 - Code review is hard work, and it is a relatively thankless occupation;
120 longer-term work.
135 is that conflicts with work being done by others turn up. In the worst
136 case, heavy patch conflicts can result in some work being put on the back
140 everything applies cleanly. This work can be a pain, but count your
169 negating all of the work you have done to get your patch into the mainline,
171 well make it harder for you to get work merged in the future.
[all …]
|
| D | contribution-maturity-model.rst | 69 ACM, etc.), are considered part of an engineer’s work.
91 * Software Engineers are encouraged to spend a portion of their work
92 time focused on Upstream Work, which is defined as reviewing patches,
105 at least a third of the engineer’s time spent doing Upstream Work.
109 Upstream Work to work focused on directly pursuing business goals.
|
| D | 5.Posting.rst | 6 Sooner or later, the time comes when your work is ready to be presented to
22 work being done is complex, though, there is a lot to be gained by getting
23 feedback from the community before the work is complete. So you should
24 consider posting in-progress work, or even making a git tree available so
25 that interested developers can catch up with your work at any time.
28 good idea to say so in the posting itself. Also mention any major work
31 with the idea that they can help you drive the work in the right direction.
52 - Be sure that you have the right to post the code. If this work was done
53 for an employer, the employer likely has a right to the work and must be
63 The preparation of patches for posting can be a surprising amount of work,
[all …]
|
| D | 1.Intro.rst | 36 possible reception for your work.
83 difficulties when trying to do kernel work. The kernel community has
102 better; the following text should help you - or those who work for you -
114 This work was supported by the Linux Foundation; thanks especially to
121 learning how to work with the kernel community and get their code into the
144 constant upkeep if it is to work with new kernels. Maintaining
145 out-of-tree code requires significant amounts of work just to keep that
148 Code which is in the mainline, instead, does not require this work as the
169 to implement changes which make the kernel work better for their needs.
180 process work. By contributing your code you can add new functionality to
|
| /Documentation/usb/ |
| D | gadget_multi.rst | 26 To make use of the gadget one needs to make it work on host side --
40 configuration with CDC ECM which should work better under Linux.
45 For the gadget to work under Windows two conditions have to be met:
60 configuration so a dual RNDIS and CDC ECM gadget won't work unless you
97 functionality. As an effect provided INFs won't work since they have
107 things don't work as intended before realising Windows have cached
115 and Windows 7, all 32-bit versions. It should work on 64-bit versions
116 as well. It most likely won't work on Windows prior to Windows XP
124 believed that it should (read: "I have no idea whether it will") work
|
| /Documentation/driver-api/driver-model/ |
| D | design-patterns.rst | 69 Continuing on the above example we add an offloaded work::
78 static void foo_work(struct work_struct *work)
80 struct foo *foo = container_of(work, struct foo, offload);
112 for this to work.
116 work function to a single pointer.
|
| /Documentation/translations/zh_CN/scheduler/ |
| D | sched-capacity.rst | 74 CPU0 work ^
79 CPU1 work ^
103 CPU0 work ^
109 CPU1 work ^
143 CPU work ^
152 CPU work ^
179 CPU0 work ^
184 CPU1 work ^
340 CPU work ^
347 CPU work ^
|
| /Documentation/power/ |
| D | basic-pm-debugging.rst | 17 hibernation is most likely to work correctly. Still, you need to repeat the
22 systems might be necessary to make hibernation work. Thus, if your machine
31 Unfortunately, the "platform" mode of hibernation does not work on some systems
33 work::
138 of hibernation is not likely to work. You can try the "shutdown" mode, but that
142 work (of course, this only may be an issue on SMP systems) and the problem
160 If all of the hibernation test modes work, you can boot the system with the
162 "reboot", "shutdown" and "platform" modes. If that does not work, there
193 works every time, but resume from actual hibernation does not work or is
206 In case that hibernation does not work on your system even in the minimal
[all …]
|
| /Documentation/arch/x86/ |
| D | sva.rst | 35 the use of Shared Work Queues (SWQ) by both applications and Virtual
38 allow the hardware to distinguish the context for which work is being
51 work descriptor to a device. The descriptor includes the operation to be
95 from this process. When a user submits a work descriptor to a device using the
119 IA32_PASID MSR lazily when a thread tries to submit a work descriptor
147 MMIO portal they cannot submit new work to the device.
173 work in the same address space, i.e., to share it. Some call it Shared
188 consider doorbells as a mechanism of informing hardware about work to process.
192 hardware also manages the queue depth for Shared Work Queues (SWQ), and
204 used with ENQCMD to submit work, the device can distinguish the process
[all …]
|
| /Documentation/doc-guide/ |
| D | contributing.rst | 8 developers work more effectively. Without top-quality documentation, a lot
35 people ignore them, and they will never notice when their work adds new
135 is necessary to work out what the role of those members or parameters is
153 the full value of the work that has gone into creating them.
207 current, adding whatever information is needed. Such work often requires
253 to continue. There are a couple of challenges associated with this work,
255 who work with those files; they are understandably unenthusiastic about
260 managed to turn a big pile into a group of smaller piles. The work of
288 Development work on rst2pdf seems to have picked up again in recent times,
290 work with that project to make rst2pdf work with the kernel documentation
|
| /Documentation/networking/ |
| D | net_dim.rst | 44 #. Applies a schedule work function, which applies suggested configuration.
74 suggested configuration. This is done by scheduling a work function, defined by
79 it and it would be useless if the work function would not apply the suggested
119 the data flow. After the work is done, Net DIM algorithm needs to be set to
134 void my_driver_do_dim_work(struct work_struct *work)
137 struct dim *dim = container_of(work, struct dim,
138 work);
142 /* Signal net DIM work is done and it should move to next iteration */
168 INIT_WORK(&my_entity->dim.work, my_driver_do_dim_work);
|
| /Documentation/fb/ |
| D | sstfb.rst | 10 video boards. It's highly experimental code, but is guaranteed to work
15 you want the latest version, check out the CVS, as the driver is a work
30 This driver (should) work on ix86, with "late" 2.2.x kernel (tested
85 (how does it work with vgacon ? short answer : it doesn't work)
115 doesn't work yet...
169 - The driver is 16 bpp only, 24/32 won't work.
186 - The 24/32 is not likely to work anytime soon, knowing that the
|
| D | vesafb.rst | 13 impossible; BIOS calls work in real mode only. VESA BIOS Extensions
74 If this does not work, this might be because your BIOS does not support
82 2. Note: Some newer versions of LILO appear to work with those hex values,
88 XF68_FBDev should work just fine, but it is non-accelerated. Running
89 another (accelerated) X-Server like XF86_SVGA might or might not work.
107 * VBE 3.0 might work too. I have neither a gfx board with VBE 3.0
117 seems not to work with some BIOS versions, but there are options
|
| /Documentation/hwmon/ |
| D | asb100.rst | 32 controller will simply not work (or maybe it will for you... it doesn't for
43 processor should work with. This is hardcoded by the mainboard and/or
46 Alarms: (TODO question marks indicate may or may not work)
|
| /Documentation/scsi/ |
| D | qlogicfas.rst | 77 I noticed my system which seems to work 100% would fail this test if
83 work less well because of the heat, or when cables get too long for
86 Remember, if it doesn't work under DOS, it probably won't work under
|
| /Documentation/sound/cards/ |
| D | maya44.rst | 20 ESI provided a sample Maya44 card for the development work.
27 The following functions work, as tested by Rainer Zimmermann and Piotr Makowski:
37 The following functions *should* work, but are not fully tested:
48 Things that do not seem to work:
52 - Ardour 2.1 seems to work only via JACK, not using ALSA directly or via OSS. This still needs to b…
103 *AVOID CAPTURING AT RATES ABOVE 96kHz*, even though it may appear to work. The codec cannot actuall…
|
| /Documentation/scheduler/ |
| D | sched-capacity.rst | 73 With a workload that periodically does a fixed amount of work, you will get an
76 CPU0 work ^
81 CPU1 work ^
87 work W in T units of time. On the other hand, CPU1 has half the capacity of
107 CPU0 work ^
113 CPU1 work ^
156 CPU work ^
165 CPU work ^
171 behaviour (i.e. executing the same amount of work) in both executions.
196 CPU0 work ^
[all …]
|
| /Documentation/ |
| D | index.rst | 10 documentation, like the kernel itself, is very much a work in progress;
11 that is especially true as we work to integrate our many scattered
20 community and getting your work upstream.
69 trying to get it to work optimally on a given system and application
|
| /Documentation/locking/ |
| D | pi-futex.rst | 7 - in the user-space fastpath a PI-enabled futex involves no kernel work
79 mutexes involves no kernel work at all - they behave quite similarly to
92 remaining work: if there is no futex-queue attached to the futex address
100 futex value to its own TID and returns. Userspace has no other work to
105 TID -> 0 atomic transition of the futex value], then no kernel work is
|
12345678910>>...38