netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Evgeniy Polyakov <zbr@ioremap.net>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: James Morris <jmorris@namei.org>, Li Zefan <lizf@cn.fujitsu.com>,
	David Miller <davem@davemloft.net>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] connector: create connector workqueue only while needed once
Date: Mon, 2 Feb 2009 14:06:13 +0300	[thread overview]
Message-ID: <20090202110613.GA11413@ioremap.net> (raw)
In-Reply-To: <498638ad.1438560a.537e.51b8@mx.google.com>

Hi.

On Sun, Feb 01, 2009 at 04:05:01PM -0800, Frederic Weisbecker (fweisbec@gmail.com) wrote:
> The netlink connector uses its own workqueue to relay the datas sent from
> userspace to the appropriate callback.
> If you launch the test from Documentation/connector and change it a bit to send
> a high flow of data, you will see thousands of events coming to the "cqueue" workqueue
> by looking at the workqueue tracer.
> 
> This flow of events can be sent very quickly. So, to not encumber the kevent workqueue and
> delay other jobs, the "cqueue" workqueue should remain.
> 
> But this workqueue is pointless most of the time, it will always be created (assuming you have
> built it of course) although only developpers with specific needs will use it.
> 
> So avoid this "most of the time useless task", this patch proposes to create this workqueue only when needed
> once.
> The first jobs to be sent to connector callbacks will be sent to kevent while the "cqueue" thread creation
> will be scheduled to kevent too.
> 
> The following jobs will continue to be scheduled to keventd until the cqueue workqueue is created, and then
> the rest of the jobs will continue to perform as usual, through this dedicated workqueue.
> 
> Each time I tested this patch, only the first event was sent to keventd, the rest has been sent to cqueue which
> have been created quickly.
> 
> Also, this patch fixes some trailing whitespaces on the connector files.
> 
> Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>

Looks very good, thanks a lot Frederic.
Ack.

-- 
	Evgeniy Polyakov

  reply	other threads:[~2009-02-02 11:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-02  0:05 [PATCH] connector: create connector workqueue only while needed once Frederic Weisbecker
2009-02-02 11:06 ` Evgeniy Polyakov [this message]
2009-02-03  7:22   ` David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090202110613.GA11413@ioremap.net \
    --to=zbr@ioremap.net \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=fweisbec@gmail.com \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).