Searched full:work (Results 1 – 25 of 773) sorted by relevance
12345678910>>...31
| /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)
55 - Long Li (some great work on RDMA, SMB Direct)
|
| /Documentation/ |
| D | padata.txt | 7 Padata is a mechanism by which the kernel can farm work out to be done in
25 The pcpumask describes which processors will be used to execute work
28 The workqueue wq is where the work will actually be done; it should be
50 if that flag is not set, other functions will refuse to work.
102 Actually submitting work to the padata instance requires the creation of a
112 structure specific to the work to be done. Most of its fields are private to
115 be called in the process of getting the work done as we will see
118 The submission of work is done with::
124 specifies which CPU will be used for the final callback when the work is
126 padata_do_parallel() is zero on success, indicating that the work is in
[all …]
|
| D | pi-futex.txt | 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
|
| /Documentation/networking/device_drivers/qlogic/ |
| D | LICENSE.qlge | 72 0. This License applies to any program or other work which contains
75 refers to any such program or work, and a "work based on the Program"
76 means either the Program or any derivative work under copyright law:
77 that is to say, a work containing the Program or a portion of it,
85 is covered only if its contents constitute a work based on the
101 of it, thus forming a work based on the Program, and copy and
102 distribute such modifications or work under the terms of Section 1
108 b) You must cause any work that you distribute or publish, that in
121 does not normally print such an announcement, your work based on
124 These requirements apply to the modified work as a whole. If
[all …]
|
| D | LICENSE.qlcnic | 72 0. This License applies to any program or other work which contains
75 refers to any such program or work, and a "work based on the Program"
76 means either the Program or any derivative work under copyright law:
77 that is to say, a work containing the Program or a portion of it,
85 is covered only if its contents constitute a work based on the
101 of it, thus forming a work based on the Program, and copy and
102 distribute such modifications or work under the terms of Section 1
108 b) You must cause any work that you distribute or publish, that in
121 does not normally print such an announcement, your work based on
124 These requirements apply to the modified work as a whole. If
[all …]
|
| /Documentation/scsi/ |
| D | LICENSE.qla4xxx | 73 0. This License applies to any program or other work which contains
76 refers to any such program or work, and a "work based on the Program"
77 means either the Program or any derivative work under copyright law:
78 that is to say, a work containing the Program or a portion of it,
86 is covered only if its contents constitute a work based on the
102 of it, thus forming a work based on the Program, and copy and
103 distribute such modifications or work under the terms of Section 1
109 b) You must cause any work that you distribute or publish, that in
122 does not normally print such an announcement, your work based on
125 These requirements apply to the modified work as a whole. If
[all …]
|
| D | LICENSE.qla2xxx | 74 0. This License applies to any program or other work which contains
77 refers to any such program or work, and a "work based on the Program"
78 means either the Program or any derivative work under copyright law:
79 that is to say, a work containing the Program or a portion of it,
87 is covered only if its contents constitute a work based on the
103 of it, thus forming a work based on the Program, and copy and
104 distribute such modifications or work under the terms of Section 1
110 b) You must cause any work that you distribute or publish, that in
123 does not normally print such an announcement, your work based on
126 These requirements apply to the modified work as a whole. If
[all …]
|
| D | qlogicfas.txt | 68 I noticed my system which seems to work 100% would fail this test if
74 work less well because of the heat, or when cables get too long for
77 Remember, if it doesn't work under DOS, it probably won't work under
|
| /Documentation/media/dvb-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
|
| /Documentation/media/v4l-drivers/ |
| 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;
113 longer-term work.
128 is that conflicts with work being done by others turn up. In the worst
129 case, heavy patch conflicts can result in some work being put on the back
133 everything applies cleanly. This work can be a pain, but count your
162 negating all of the work you have done to get your patch into the mainline,
164 well make it harder for you to get work merged in the future.
[all …]
|
| D | 5.Posting.rst | 6 Sooner or later, the time comes when your work is ready to be presented to
23 work being done is complex, though, there is a lot to be gained by getting
24 feedback from the community before the work is complete. So you should
25 consider posting in-progress work, or even making a git tree available so
26 that interested developers can catch up with your work at any time.
29 good idea to say so in the posting itself. Also mention any major work
32 with the idea that they can help you drive the work in the right direction.
53 - Be sure that you have the right to post the code. If this work was done
54 for an employer, the employer likely has a right to the work and must be
64 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/networking/ |
| D | net_dim.txt | 51 4. Applies a schedule work function, which applies suggested configuration.
81 suggested configuration. This is done by scheduling a work function, defined by
86 it and it would be useless if the work function would not apply the suggested
123 the data flow. After the work is done, Net DIM algorithm needs to be set to
138 void my_driver_do_dim_work(struct work_struct *work)
141 struct dim *dim = container_of(work, struct dim,
142 work);
146 /* Signal net DIM work is done and it should move to next iteration */
172 INIT_WORK(&my_entity->dim.work, my_driver_do_dim_work);
|
| D | cops.txt | 11 Right now these cards are known to work with the COPS driver. The
12 LT-200 cards work in a somewhat more limited capacity than the
13 DL200 cards, which work very well and are in use by many people.
49 it work with the cops.c driver.
|
| /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/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/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/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/arm/omap/ |
| D | omap.rst | 12 CONFIG_REGULATOR_PBIAS is enabled for MMC1 to work
17 to work in DRA7 and K2G based boards.
|
| /Documentation/misc-devices/ |
| D | bh1770glc.txt | 32 by using a delayed work. As long as there is proximity threshold above
33 interrupts the delayed work is pushed forward. So, when proximity level goes
34 below the threshold value, there is no interrupt and the delayed work will
|
12345678910>>...31