linux-kernel - Re: IPC between application and xserver is causing extra context switches

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 3 Sep 2010 11:06:42 +0300
From:	Pauli Nieminen <ext-pauli.nieminen@...ia.com>
To:	ext Peter Zijlstra <peterz@...radead.org>
Cc:	ext Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
	Tony Lindgren <tony@...mide.com>,
	Jarkko Nikula <jhnikula@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Pauli <suokkos@...il.com>
Subject: Re: IPC between application and xserver is causing extra context
 switches

On 03/09/10 09:31 +0200, ext Peter Zijlstra wrote:
> On Fri, 2010-09-03 at 10:17 +0300, Pauli Nieminen wrote:
> > Scheduling at write is wrong because xserver doesn't know about client
> > priorities. 
> 
> Waking up the client at write is correct because you don't know if there
> is more to be written.
> 
> Really, your assumptions about when things schedule is wrong.
> 
>

Where is it wrong?

I'm just explaining what I have seen in trace output. I also try to explain
why it is wrong for xserver/client communication.

If problems that I see aren't scheduling problems then xserver has to
understand client priorities and duplicate scheduler code in user space.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/