search for: wq

...ssing off the work from the irq into a workqueue. > > > > > > > > > > > > > > > > Signed-off-by: Dave Airlie <airlied at redhat.com> > > > > > > > > > > > > > > Nouveau's scheduler uses a dedicated wq, hence from this perspective it's > > > > > > > safe deferring fence signalling to the kernel global wq. However, I wonder > > > > > > > if we could create deadlocks by building dependency chains into other > > > > > > > drivers / k...

...n not figure out why it is not working. i have gone through the FAQs and have found nothing (not to say I might have missed something). I am highly embarrased with my inability find the problem (my face is bright red!) I am using R 1.8.1 on win xp. Below is the resluts of my manual testing: > Wq <- (1+k*(Qa-(k/(6*n))))^(1/3) > Wq [1] NaN > Wq <- (1+k*(Qa-(k/(6*n)))) > Wq [1] -10.72508 > Wq <- Wq^(1/3) > Wq [1] NaN > z <- -10.72508^(1/3) > z [1] -2.205296 as you can see if Wq = -10.72508, Wq^(1/3) is NaN but z<- -10.72508^(1/3) returns a number. If so...

...is an example of stepAIC that I do not understand. The data is n=42, Lage is the only factor and there are four other variables treated as continuous. First you see the stepAIC-forward solution (fs7). The strange thing here is that apparently not all interactions are tried for inclusion, but only WQ:Lage. In particular, I think that WFL:Lage should be tried in the last two steps, where WFL and Lage are already in the fit. After fs7, I give the output of fs6 (backward), where all interactions are tried as I have expected. (regsubsets works properly forward and backward.) Do I misunderstand som...

...ello, I am trying to decide which package to use to calculate the non-parametric Sen's Slope for identifying trends in rainfall data (determine the slope between all pairs of points and take the median of those slopes). I have found three packages that output Sen's: "zyp", "wq" and "fume". The outputs of "zyp.sen()" and "mannKen()" from the zyp and wq packages match, but the output from fume's "mkTrend" is different. I tried looking at the code from these three and I could not really understand what zyp and wq are doing...

...> } > > > > > > Shouldn't the work item be flushed before removal is complete? > > > > In fact, flushing it won't help because it can requeue itself, right? There's cancel_work_sync() to stop the self-requeueing ones. > From that POV a dedicated WQ kept it simple. A dedicated wq doesn't do anything for that. You can't shut down a workqueue with a pending work item on it. destroy_workqueue() will try to drain the target wq, warn if it doesn't finish in certain number of iterations and just keep trying indefinitely. Thanks. --...

...> } > > > > > > Shouldn't the work item be flushed before removal is complete? > > > > In fact, flushing it won't help because it can requeue itself, right? There's cancel_work_sync() to stop the self-requeueing ones. > From that POV a dedicated WQ kept it simple. A dedicated wq doesn't do anything for that. You can't shut down a workqueue with a pending work item on it. destroy_workqueue() will try to drain the target wq, warn if it doesn't finish in certain number of iterations and just keep trying indefinitely. Thanks. --...

...use a struct initializer instead of a > > memset(0)+field-assignment? > > > > struct drm_sched_init_params sched_params = { Actually, you can even make it const if it's not modified after the declaration. > > .ops = &panthor_queue_sched_ops, > > .submit_wq = group->ptdev->scheduler->wq, > > .num_rqs = 1, > > .credit_limit = args->ringbuf_size / sizeof(u64), > > .hang_limit = 0, > > .timeout = msecs_to_jiffies(JOB_TIMEOUT_MS), > > .timeout_wq = group->ptdev->reset.wq, > > .name = "...

...t; > memset(0)+field-assignment? > > > > > > struct drm_sched_init_params sched_params = { > > Actually, you can even make it const if it's not modified after the > declaration. > > > > .ops = &panthor_queue_sched_ops, > > > .submit_wq = group->ptdev->scheduler->wq, > > > .num_rqs = 1, > > > .credit_limit = args->ringbuf_size / sizeof(u64), > > > .hang_limit = 0, > > > .timeout = msecs_to_jiffies(JOB_TIMEOUT_MS), > > > .timeout_wq = group->ptdev->reset.wq, &...

...ork item has to be scheduled from fill_balloon() and leak_balloon() when they do not do all requested changes in a single call. I think that performance is not the most critical thing in this case. Anyway, I tried to create the workqueue two ways: 1st create_freezable_workqueue("vballoon_wq"); 2nd alloc_workqueue("vballoon_wq", WQ_FREEZABLE | WQ_MEM_RECLAIM, 0); And then I tried to modify 10 times the size of a virtual host by ballooning between 20GB and 2GB. I got the following times: ----------------------------------------------------- | | kthre...

...ork item has to be scheduled from fill_balloon() and leak_balloon() when they do not do all requested changes in a single call. I think that performance is not the most critical thing in this case. Anyway, I tried to create the workqueue two ways: 1st create_freezable_workqueue("vballoon_wq"); 2nd alloc_workqueue("vballoon_wq", WQ_FREEZABLE | WQ_MEM_RECLAIM, 0); And then I tried to modify 10 times the size of a virtual host by ballooning between 20GB and 2GB. I got the following times: ----------------------------------------------------- | | kthre...

...ak_balloon() when they do not do all requested changes in a single call. Changes in v2: + More elegant detection of the pending work in fill_balloon() and leak_ballon(). It still needs to keep the original requested number of pages but it does not add any extra boolean variable. + Remove WQ_MEM_RECLAIM workqueue parameter. If I get it correctly, this is possible because the code manipulates memory but it is not used in the memory reclaim path. + initialize the work item before allocation the workqueue Signed-off-by: Petr Mladek <pmladek at suse.cz> --- drivers/virtio/v...

...ak_balloon() when they do not do all requested changes in a single call. Changes in v2: + More elegant detection of the pending work in fill_balloon() and leak_ballon(). It still needs to keep the original requested number of pages but it does not add any extra boolean variable. + Remove WQ_MEM_RECLAIM workqueue parameter. If I get it correctly, this is possible because the code manipulates memory but it is not used in the memory reclaim path. + initialize the work item before allocation the workqueue Signed-off-by: Petr Mladek <pmladek at suse.cz> --- drivers/virtio/v...

Using the kernel global workqueue to signal fences can lead to unexpected deadlocks. Some other work (e.g. from a different driver) could directly or indirectly depend on this fence to be signaled. However, if the WQ_MAX_ACTIVE limit is reached by waiters, this can prevent the work signaling the fence from running. While this seems fairly unlikely, it's potentially exploitable. Fixes: 39126abc5e20 ("nouveau: offload fence uevents work to workqueue") Signed-off-by: Danilo Krummrich <dakr at re...

Dear R-users, tsboot fails when I try to perform a block bootstrap on seaKen (package wq): these commands: require(wq) require(datasets) boot.block.sen <- function(data){seaKen(data)[[1]]} tsboot(sunspot.month, boot.block.sen, R=1999, l=12, sim="fixed") return: Error in seaKen(data) : x must be a 'ts' Any suggestion on how might I change seaKen in order to use...

This is bug or feature ?! For all reply I got this message. ----- Forwarded message from Mail Delivery System <Mailer-Daemon at mail.acampo.net> ----- To: milon at wq.cz Subject: Mail delivery failed: returning message to sender From: Mail Delivery System <Mailer-Daemon at mail.acampo.net> Date: Sun, 4 Nov 2007 22:29:14 +0100 The original message was received at Sun, 4 Nov 2007 22:29:14 +0100 from milon at wq.cz by Acampo.net Error: No space left in th...

...h <dakr at redhat.com> wrote: > > > > Using the kernel global workqueue to signal fences can lead to > > unexpected deadlocks. Some other work (e.g. from a different driver) > > could directly or indirectly depend on this fence to be signaled. > > However, if the WQ_MAX_ACTIVE limit is reached by waiters, this can > > prevent the work signaling the fence from running. > > > > While this seems fairly unlikely, it's potentially exploitable. > > LGTM > > Reviewed-by: Dave Airlie <airlied at redhat.com> > > probably...

...0) == > >> + VPORT_STATE_UP) > >> + return true; > >> + > >> + return false; > >> +} > >> + > >> +static void update_carrier(struct work_struct *work) > >> +{ > >> + struct mlx5_vdpa_wq_ent *wqent; > >> + struct mlx5_vdpa_dev *mvdev; > >> + struct mlx5_vdpa_net *ndev; > >> + > >> + wqent = container_of(work, struct mlx5_vdpa_wq_ent, work); > >> + mvdev = wqent->mvdev; > >> + ndev = to_mlx5_vdpa_...

...@@ -2844,12 +2847,18 @@ static int amdgpu_device_init_schedulers(struct amdgpu_device *adev) break; } - r = drm_sched_init(&ring->sched, &amdgpu_sched_ops, NULL, - DRM_SCHED_PRIORITY_COUNT, - ring->num_hw_submission, 0, - timeout, adev->reset_domain->wq, - ring->sched_score, ring->name, - adev->dev); + params.ops = &amdgpu_sched_ops; + params.submit_wq = NULL; /* Use the system_wq. */ + params.num_rqs = DRM_SCHED_PRIORITY_COUNT; + params.credit_limit = ring->num_hw_submission; + params.hang_limit = 0; + params.tim...

...ancel_work_sync is in progress? > Does it fail to queue? cancel_work_sync() is guaranteed to take self-requeueing work items no matter when it's called or what's going on. External (non-self) queueings of course should be stopped in other ways. > > > From that POV a dedicated WQ kept it simple. > > > > A dedicated wq doesn't do anything for that. You can't shut down a > > workqueue with a pending work item on it. destroy_workqueue() will > > try to drain the target wq, warn if it doesn't finish in certain > > number of iteration...

...ancel_work_sync is in progress? > Does it fail to queue? cancel_work_sync() is guaranteed to take self-requeueing work items no matter when it's called or what's going on. External (non-self) queueings of course should be stopped in other ways. > > > From that POV a dedicated WQ kept it simple. > > > > A dedicated wq doesn't do anything for that. You can't shut down a > > workqueue with a pending work item on it. destroy_workqueue() will > > try to drain the target wq, warn if it doesn't finish in certain > > number of iteration...