FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Cluster Development

 
 
LinkBack Thread Tools
 
Old 11-12-2010, 11:12 AM
Steven Whitehouse
 
Default dlm: Use cmwq for send and receive workqueues

So far as I can tell, there is no reason to use a single-threaded
send workqueue for dlm, since it may need to send to several sockets
concurrently. Both workqueues are set to WQ_MEM_RECLAIM to avoid
any possible deadlocks, WQ_HIGHPRI since locking traffic is highly
latency sensitive (and to avoid a priority inversion wrt GFS2's
glock_workqueue) and WQ_FREEZABLE just in case someone needs to do
that (even though with current cluster infrastructure, it doesn't
make sense as the node will most likely land up ejected from the
cluster) in the future.

Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
Cc: Tejun Heo <tj@kernel.org>

diff --git a/fs/dlm/lowcomms.c b/fs/dlm/lowcomms.c
index 37a34c2..0893b30 100644
--- a/fs/dlm/lowcomms.c
+++ b/fs/dlm/lowcomms.c
@@ -1431,14 +1431,16 @@ static void work_stop(void)
static int work_start(void)
{
int error;
- recv_workqueue = create_workqueue("dlm_recv");
+ recv_workqueue = alloc_workqueue("dlm_recv", WQ_MEM_RECLAIM |
+ WQ_HIGHPRI | WQ_FREEZEABLE, 0);
error = IS_ERR(recv_workqueue);
if (error) {
log_print("can't start dlm_recv %d", error);
return error;
}

- send_workqueue = create_singlethread_workqueue("dlm_send");
+ send_workqueue = alloc_workqueue("dlm_send", WQ_MEM_RECLAIM |
+ WQ_HIGHPRI | WQ_FREEZEABLE, 0);
error = IS_ERR(send_workqueue);
if (error) {
log_print("can't start dlm_send %d", error);
 
Old 11-12-2010, 03:12 PM
David Teigland
 
Default dlm: Use cmwq for send and receive workqueues

On Fri, Nov 12, 2010 at 12:12:29PM +0000, Steven Whitehouse wrote:
>
> So far as I can tell, there is no reason to use a single-threaded
> send workqueue for dlm, since it may need to send to several sockets
> concurrently. Both workqueues are set to WQ_MEM_RECLAIM to avoid
> any possible deadlocks, WQ_HIGHPRI since locking traffic is highly
> latency sensitive (and to avoid a priority inversion wrt GFS2's
> glock_workqueue) and WQ_FREEZABLE just in case someone needs to do
> that (even though with current cluster infrastructure, it doesn't
> make sense as the node will most likely land up ejected from the
> cluster) in the future.

Thanks, I'll want to do some testing with this, but my test machines do
not seem to create more than one dlm_recv workqueue thread (prior to this
patch). Have you tested in any cases where many threads end up being
created? I've noticed while debugging some many-cpu machines a huge
number of dlm_recv threads, which is just excessive. Does this patch
address that?


> Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
> Cc: Tejun Heo <tj@kernel.org>
>
> diff --git a/fs/dlm/lowcomms.c b/fs/dlm/lowcomms.c
> index 37a34c2..0893b30 100644
> --- a/fs/dlm/lowcomms.c
> +++ b/fs/dlm/lowcomms.c
> @@ -1431,14 +1431,16 @@ static void work_stop(void)
> static int work_start(void)
> {
> int error;
> - recv_workqueue = create_workqueue("dlm_recv");
> + recv_workqueue = alloc_workqueue("dlm_recv", WQ_MEM_RECLAIM |
> + WQ_HIGHPRI | WQ_FREEZEABLE, 0);
> error = IS_ERR(recv_workqueue);
> if (error) {
> log_print("can't start dlm_recv %d", error);
> return error;
> }
>
> - send_workqueue = create_singlethread_workqueue("dlm_send");
> + send_workqueue = alloc_workqueue("dlm_send", WQ_MEM_RECLAIM |
> + WQ_HIGHPRI | WQ_FREEZEABLE, 0);
> error = IS_ERR(send_workqueue);
> if (error) {
> log_print("can't start dlm_send %d", error);
>
>
 
Old 11-12-2010, 03:20 PM
Steven Whitehouse
 
Default dlm: Use cmwq for send and receive workqueues

Hi,

On Fri, 2010-11-12 at 11:12 -0500, David Teigland wrote:
> On Fri, Nov 12, 2010 at 12:12:29PM +0000, Steven Whitehouse wrote:
> >
> > So far as I can tell, there is no reason to use a single-threaded
> > send workqueue for dlm, since it may need to send to several sockets
> > concurrently. Both workqueues are set to WQ_MEM_RECLAIM to avoid
> > any possible deadlocks, WQ_HIGHPRI since locking traffic is highly
> > latency sensitive (and to avoid a priority inversion wrt GFS2's
> > glock_workqueue) and WQ_FREEZABLE just in case someone needs to do
> > that (even though with current cluster infrastructure, it doesn't
> > make sense as the node will most likely land up ejected from the
> > cluster) in the future.
>
> Thanks, I'll want to do some testing with this, but my test machines do
> not seem to create more than one dlm_recv workqueue thread (prior to this
> patch). Have you tested in any cases where many threads end up being
> created? I've noticed while debugging some many-cpu machines a huge
> number of dlm_recv threads, which is just excessive. Does this patch
> address that?
>
>
Yes, one of the features of the cmwq is that you land up with only as
many threads as required. When threads block, new ones are created to
avoid stalling the workqueue. Workqueues marked with WQ_MEM_RECLAIM
create a single rescuer thread, otherwise the threads are shared with
all other users of cmwq,

Steve.

> > Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
> > Cc: Tejun Heo <tj@kernel.org>
> >
> > diff --git a/fs/dlm/lowcomms.c b/fs/dlm/lowcomms.c
> > index 37a34c2..0893b30 100644
> > --- a/fs/dlm/lowcomms.c
> > +++ b/fs/dlm/lowcomms.c
> > @@ -1431,14 +1431,16 @@ static void work_stop(void)
> > static int work_start(void)
> > {
> > int error;
> > - recv_workqueue = create_workqueue("dlm_recv");
> > + recv_workqueue = alloc_workqueue("dlm_recv", WQ_MEM_RECLAIM |
> > + WQ_HIGHPRI | WQ_FREEZEABLE, 0);
> > error = IS_ERR(recv_workqueue);
> > if (error) {
> > log_print("can't start dlm_recv %d", error);
> > return error;
> > }
> >
> > - send_workqueue = create_singlethread_workqueue("dlm_send");
> > + send_workqueue = alloc_workqueue("dlm_send", WQ_MEM_RECLAIM |
> > + WQ_HIGHPRI | WQ_FREEZEABLE, 0);
> > error = IS_ERR(send_workqueue);
> > if (error) {
> > log_print("can't start dlm_send %d", error);
> >
> >
 
Old 11-12-2010, 07:03 PM
David Teigland
 
Default dlm: Use cmwq for send and receive workqueues

On Fri, Nov 12, 2010 at 04:20:35PM +0000, Steven Whitehouse wrote:
> Hi,
>
> On Fri, 2010-11-12 at 11:12 -0500, David Teigland wrote:
> > On Fri, Nov 12, 2010 at 12:12:29PM +0000, Steven Whitehouse wrote:
> > >
> > > So far as I can tell, there is no reason to use a single-threaded
> > > send workqueue for dlm, since it may need to send to several sockets
> > > concurrently. Both workqueues are set to WQ_MEM_RECLAIM to avoid
> > > any possible deadlocks, WQ_HIGHPRI since locking traffic is highly
> > > latency sensitive (and to avoid a priority inversion wrt GFS2's
> > > glock_workqueue) and WQ_FREEZABLE just in case someone needs to do
> > > that (even though with current cluster infrastructure, it doesn't
> > > make sense as the node will most likely land up ejected from the
> > > cluster) in the future.
> >
> > Thanks, I'll want to do some testing with this, but my test machines do
> > not seem to create more than one dlm_recv workqueue thread (prior to this
> > patch). Have you tested in any cases where many threads end up being
> > created? I've noticed while debugging some many-cpu machines a huge
> > number of dlm_recv threads, which is just excessive. Does this patch
> > address that?
> >
> >
> Yes, one of the features of the cmwq is that you land up with only as
> many threads as required. When threads block, new ones are created to
> avoid stalling the workqueue. Workqueues marked with WQ_MEM_RECLAIM
> create a single rescuer thread, otherwise the threads are shared with
> all other users of cmwq,

Thanks, pushed to
git://git.kernel.org/pub/scm/linux/kernel/git/teigland/dlm.git#next
 

Thread Tools




All times are GMT. The time now is 04:34 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org