From: Peter Ujfalusi <peter.ujfalusi@nokia.com>
To: ext Andy Walls <awalls@radix.net>
Cc: ext Mark Brown <broonie@opensource.wolfsonmicro.com>,
ext Tejun Heo <tj@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Takashi Iwai <tiwai@suse.de>
Subject: Re: linux-next: workqueues tree build failure
Date: Thu, 26 Nov 2009 15:23:40 +0200 [thread overview]
Message-ID: <200911261523.40952.peter.ujfalusi@nokia.com> (raw)
In-Reply-To: <1259239796.3062.20.camel@palomino.walls.org>
On Thursday 26 November 2009 14:49:56 ext Andy Walls wrote:
>
> Peter,
>
> I would suspect using a single-threaded workqueue is better than a
> wake_up() of another thread. IIRC, after queuing work, the workqueue's
> single thread may run almost immediately on the same processor. With
> waking up sleeping threads, I've run into scheduler delays around 10 ms
> on a dual core x86_64 desktop system.
Hello Andy,
I have sent the patch which changes from rt to singlethread, I hope it fixes the
breakage in linux-next.
In short testing, when there is virtually no load on the system I can not see
any difference, which might change later.
But I'll keep in mind that probably I'm not going to better off with the waking
up of a sleeping thread.
>
> Regards,
> Andy
Thanks,
Péter
next prev parent reply other threads:[~2009-11-26 13:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 8:00 linux-next: workqueues tree build failure Stephen Rothwell
2009-11-26 8:04 ` Tejun Heo
2009-11-26 8:16 ` Peter Ujfalusi
2009-11-26 9:12 ` Tejun Heo
2009-11-26 9:24 ` Takashi Iwai
2009-11-26 9:31 ` Peter Ujfalusi
2009-11-26 10:18 ` Mark Brown
2009-11-26 11:44 ` Peter Ujfalusi
2009-11-26 12:49 ` Andy Walls
2009-11-26 13:23 ` Peter Ujfalusi [this message]
2009-11-26 12:40 ` Andy Walls
2009-11-26 12:56 ` Mark Brown
2009-11-27 2:02 ` Tejun Heo
2009-11-27 8:37 ` Takashi Iwai
2009-11-27 8:42 ` Tejun Heo
2009-11-27 10:09 ` Peter Ujfalusi
2009-11-27 11:38 ` Mark Brown
2009-11-27 13:50 ` Andy Walls
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=200911261523.40952.peter.ujfalusi@nokia.com \
--to=peter.ujfalusi@nokia.com \
--cc=awalls@radix.net \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tiwai@suse.de \
--cc=tj@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