search for: dworks

FYI, it is likely that ocfs2 will not work on 3.7-rcN until the following one-line patch is merged, as the code in ramster that provoked it is directly leveraged from ocfs2 o2net. > From: Tejun Heo [mailto:tj at kernel.org] > Sent: Thursday, October 18, 2012 5:39 PM > To: Dan Magenheimer > Cc: linux-kernel at vger.kernel.org; Konrad Wilk > Subject: [PATCH] workqueue:

On Mon, Jul 14, 2014 at 10:05:19AM +0530, Amit Shah wrote: > Some RNG devices may not be ready to give early randomness at probe() > time, and hence lose out on the opportunity to contribute to system > randomness at boot- or device hotplug- time. > > This commit schedules a delayed work item for such devices, and fetches > early randomness after a delay. Currently the delay is

On Mon, Jul 14, 2014 at 10:05:19AM +0530, Amit Shah wrote: > Some RNG devices may not be ready to give early randomness at probe() > time, and hence lose out on the opportunity to contribute to system > randomness at boot- or device hotplug- time. > > This commit schedules a delayed work item for such devices, and fetches > early randomness after a delay. Currently the delay is

Some RNG devices may not be ready to give early randomness at probe() time, and hence lose out on the opportunity to contribute to system randomness at boot- or device hotplug- time. This commit schedules a delayed work item for such devices, and fetches early randomness after a delay. Currently the delay is 500ms, which is enough for the lone device that needs such treatment: virtio-rng. CC:

Hello, This series introduces a way to allow devices to contribute to initial system randomness after a certain delay. Specifically, the virtio-rng device can contribute initial randomness only after a successful probe(). A delayed workqueue item is queued in the system queue to fetch this randomness if the device indicates it's capable of contributing only after a delay, via the new

Hello, This series introduces a way to allow devices to contribute to initial system randomness after a certain delay. Specifically, the virtio-rng device can contribute initial randomness only after a successful probe(). A delayed workqueue item is queued in the system queue to fetch this randomness if the device indicates it's capable of contributing only after a delay, via the new

On (Mon) 14 Jul 2014 [08:37:00], Jason Cooper wrote: > On Mon, Jul 14, 2014 at 10:05:19AM +0530, Amit Shah wrote: > > Some RNG devices may not be ready to give early randomness at probe() > > time, and hence lose out on the opportunity to contribute to system > > randomness at boot- or device hotplug- time. > > > > This commit schedules a delayed work item for

On (Mon) 14 Jul 2014 [18:12:46], Amit Shah wrote: > On (Mon) 14 Jul 2014 [08:37:00], Jason Cooper wrote: > > On Mon, Jul 14, 2014 at 10:05:19AM +0530, Amit Shah wrote: > > > Some RNG devices may not be ready to give early randomness at probe() > > > time, and hence lose out on the opportunity to contribute to system > > > randomness at boot- or device hotplug-

On (Mon) 14 Jul 2014 [18:12:46], Amit Shah wrote: > On (Mon) 14 Jul 2014 [08:37:00], Jason Cooper wrote: > > On Mon, Jul 14, 2014 at 10:05:19AM +0530, Amit Shah wrote: > > > Some RNG devices may not be ready to give early randomness at probe() > > > time, and hence lose out on the opportunity to contribute to system > > > randomness at boot- or device hotplug-

Currently, it's only possible to flush on a kthread_work in contexts where it's possible to block. This can be kind of painful though when trying to implement new types of delayed work which use kthread_work, since it means we'd need to drop any spinlocks for new delayed work implementations before we can actually call kthread_flush_work(). In the time between dropping locks and

...OK - so far, so good, - however on running "smbclient -L hostname -N" from the command line on the BSD the following was generated ==> added interface ip=192.168.2.13 bcast=192.168.2.255 nmask=255.255.255.0 Anonymous login successful Domain=[DWORKS] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager] Sharename Type Comment --------- ---- ------- Error returning browse list: ERRDOS - ERRnoaccess (Access denied.) Server...

Otherwise we'll leave the packets queued until releasing vsock device. E.g., if guest is slow to start up, resulting ETIMEDOUT on connect, guest will get the connect requests from failed host sockets. Reviewed-by: Stefan Hajnoczi <stefanha at redhat.com> Signed-off-by: Peng Tao <bergwolf at gmail.com> --- net/vmw_vsock/af_vsock.c | 14 ++++++++++++++ 1 file changed, 14

Otherwise we'll leave the packets queued until releasing vsock device. E.g., if guest is slow to start up, resulting ETIMEDOUT on connect, guest will get the connect requests from failed host sockets. Reviewed-by: Stefan Hajnoczi <stefanha at redhat.com> Signed-off-by: Peng Tao <bergwolf at gmail.com> --- net/vmw_vsock/af_vsock.c | 14 ++++++++++++++ 1 file changed, 14

The current code manipulates the available transmit slots without proper locking; fix it. Signed-off-by: K. Y. Srinivasan <kys at microsoft.com> Signed-off-by: Haiyang Zhang <haiyangz at microsoft.com> Signed-off-by: Abhishek Kane <v-abkane at microsoft.com> --- drivers/staging/hv/netvsc_drv.c | 16 +++++++++------- 1 files changed, 9 insertions(+), 7 deletions(-) diff --git

The current code manipulates the available transmit slots without proper locking; fix it. Signed-off-by: K. Y. Srinivasan <kys at microsoft.com> Signed-off-by: Haiyang Zhang <haiyangz at microsoft.com> Signed-off-by: Abhishek Kane <v-abkane at microsoft.com> --- drivers/staging/hv/netvsc_drv.c | 16 +++++++++------- 1 files changed, 9 insertions(+), 7 deletions(-) diff --git

On Wed, Dec 07, 2016 at 11:14:12PM +0800, Peng Tao wrote: > Otherwise we'll leave the packets queued until releasing vsock device. > E.g., if guest is slow to start up, resulting ETIMEDOUT on connect, guest > will get the connect requests from failed host sockets. > > Reviewed-by: Stefan Hajnoczi <stefanha at redhat.com> > Signed-off-by: Peng Tao <bergwolf at

On Wed, Dec 07, 2016 at 11:14:12PM +0800, Peng Tao wrote: > Otherwise we'll leave the packets queued until releasing vsock device. > E.g., if guest is slow to start up, resulting ETIMEDOUT on connect, guest > will get the connect requests from failed host sockets. > > Reviewed-by: Stefan Hajnoczi <stefanha at redhat.com> > Signed-off-by: Peng Tao <bergwolf at

...er on running "smbclient -L > hostname -N" from the command line on the BSD > the following was generated ==> > added interface ip=192.168.2.13 bcast=192.168.2.255 > nmask=255.255.255.0 > Anonymous login successful > Domain=[DWORKS] OS=[Windows 5.0] Server=[Windows 2000 LAN > Manager] > Sharename Type Comment > --------- ---- ------- > Error returning browse list: ERRDOS - ERRnoaccess (Access > denied.) &gt...

VMware balloon enhancements: adding support for memory compaction, memory shrinker (to prevent OOM) and splitting of refused pages to prevent recurring inflations. Patches 1-2: Support for compaction Patch 3: Support for memory shrinker - disabled by default Patch 4: Split refused pages to improve performance v3->v4: * "get around to" comment [Michael] * Put list_add under page lock

VMware balloon enhancements: adding support for memory compaction, memory shrinker (to prevent OOM) and splitting of refused pages to prevent recurring inflations. Patches 1-2: Support for compaction Patch 3: Support for memory shrinker - disabled by default Patch 4: Split refused pages to improve performance v3->v4: * "get around to" comment [Michael] * Put list_add under page lock