From owner-freebsd-ports@FreeBSD.ORG Tue Apr 22 13:18:47 2014 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6AC2AEB1; Tue, 22 Apr 2014 13:18:47 +0000 (UTC) Received: from mail.kapsi.fi (mx1.kapsi.fi [IPv6:2001:1bc8:1004::1:25]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 222B21586; Tue, 22 Apr 2014 13:18:47 +0000 (UTC) Received: from 91-158-78-126.elisa-laajakaista.fi ([91.158.78.126] helo=[192.168.255.112]) by mail.kapsi.fi with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1Wcaax-0003Uu-HX; Tue, 22 Apr 2014 16:18:43 +0300 Message-ID: <53566C2F.8090309@kapsi.fi> Date: Tue, 22 Apr 2014 16:18:39 +0300 From: Arto Pekkanen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Ivan Klymenko Subject: Re: [CFT] x11-servers/xorg-server with initial (GCD) Grand Central Dispatch support References: <20140420200534.72226779@nonamehost.local> <5354E550.7050803@freebsd.org> <20140421152732.716b897b@nonamehost.local> In-Reply-To: <20140421152732.716b897b@nonamehost.local> X-Enigmail-Version: 1.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="m003oifnSVLLQSXO3S1wMnVvIniQW7O13" X-SA-Exim-Connect-IP: 91.158.78.126 X-SA-Exim-Mail-From: isoa@kapsi.fi X-SA-Exim-Scanned: No (on mail.kapsi.fi); SAEximRunCond expanded to false Cc: ports@FreeBSD.org, x11@FreeBSD.org, Niclas Zeising X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Apr 2014 13:18:47 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --m003oifnSVLLQSXO3S1wMnVvIniQW7O13 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Wow, sounds cool! I just wanted to say thank you for researching somethin= g not officially researched elsewhere :) You could fork the current X.org port, and maintain a partial ports tree = in a separate repository. Then people interested in testing the X.org wit= h GCD support could easily use http://www.freshports.org/ports-mgmt/ports= haker/ to merge your X.org with main ports tree. I've never used portshaker, nor maintained any port myself, but this seem= s like the right way to do it. On 21.4.2014 15:27, Ivan Klymenko wrote: > =D0=92 Mon, 21 Apr 2014 11:30:56 +0200 > Niclas Zeising =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >=20 >> On 04/20/14 19:05, Ivan Klymenko wrote: >>> Hi all. >>> >>> You are tired of frequent friezes xorg server? >>> Are you bored messages in /var/log/Xorg.0.log: >>> " >>> ... >>> [mi] EQ overflowing. Additional events will be discarded until >>> existing events are processed. ... >>> " >>> ? >>> >>> :) >>> >>> Then you here! :) >>> >>> Patch attached :) >>> >>> If you like, we can continue to develop this area. >> >> First of all, what is GCD. >=20 > What is GCD - for example can be read here: > http://en.wikipedia.org/wiki/Grand_Central_Dispatch >=20 >> Second of all, how does this affect the normal way things are done? >=20 > X server has a single queue of requests, which processed > sequentially. > Some applications for various reasons, either block the queue or > handled too long. > And as a result - have dead GUI (server refuses to accept new requests > for processing, until the guilty process it works), and messages > similar to the following: > " ... > [mi] EQ overflowing. Additional events will be discarded until > existing events are processed. > ... > " > or any other type of "overflowing"... > It regards changes in mi/mieq.c and mi/mipointer.c >=20 > In this case using GCD queue handled on separate threads. > GUI - always responsive. >=20 > Yes - I suspect that there is a risk of attack on xorg-server where the= > threads limit is exceeded in the system, but we can modify and somehow > eliminate in the future ... >=20 >> Thirdly, are there any plans to upstream this? >=20 > Unfortunately I'm not too familiar with the plans xorg community, > but xorg still single threaded and it s one of its key weaknesses. > I also do not have any information - whether GCD support in other > operating systems (likely they are united to advance wayland - not > xorg-server) which can be used xorg-server... So I think that these > changes will be specific only for FreeBSD. >=20 > Frankly, I think i do not have arguments and knowledge of the > English tongue, that would implement support GCD in upstream :) >=20 >> Lastly, which versions of xorg-server does this work with? >=20 > These changes were in xorg-server-1.12.4 and up... >=20 >=20 > Sorry for my english. > _______________________________________________ > freebsd-x11@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-x11 > To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org" >=20 --m003oifnSVLLQSXO3S1wMnVvIniQW7O13 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTVmwvAAoJEGSnDuw8E9qYuPEH/0hv8R/FZFjVqtz7I9PM1VrZ 0bAkHlnGalV2eDyRV/as71aMbWzYHJWgCFi1qJ1sTFDkszuMKaeh+VHFJHGDou4R TOkJ9VvDuVRUNpcFKrXAVn6QOCFlimyujEAO/iy2wju3x0ctar2WI6rVzf4ddnfh eChCHe1X4EeIeweKi+EVHzt/PM/BXVfcM3j8snlJ8yxHTd6LSBViXw59RtfNVZvz pExmxwpauaDpiaRw3QT7n0O7K9n5ndu7yKe30O9oqFNS3Fr+HmxyXO0SErOYC3cA x+RWzOHufz0sWPVVPe1peCaAl739mXaaSU1TfowlvWQDn9OrnNt84MFekmEYA0E= =9ZNg -----END PGP SIGNATURE----- --m003oifnSVLLQSXO3S1wMnVvIniQW7O13--