From: "Olinski, Krzysztof E" <krzysztof.e.olinski@intel.com>
To: "chris@chris-wilson.co.uk" <chris@chris-wilson.co.uk>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 0/2] GuC logger redesign
Date: Thu, 27 Apr 2017 09:22:11 +0000 [thread overview]
Message-ID: <1493284929.20321.1.camel@intel.com> (raw)
In-Reply-To: <20170427090546.GA5535@nuc-i3427.alporthouse.com>
[-- Attachment #1.1: Type: text/plain, Size: 652 bytes --]
On Thu, 2017-04-27 at 10:05 +0100, Chris Wilson wrote:
> On Thu, Apr 27, 2017 at 10:59:18AM +0200, Krzysztof E. Olinski wrote:
> > GuC logger implementation simplified and moved to a library
> > (GuCLAW).
> > Adds simple buffering utility for logging routine (BUC).
>
> Bigger question, why? What designs goals do you want to achieve?
> -Chris
>
Currently, there are problems with compilation for Android platform due
to pthread dependencies. The proposed implementation should work both
for Linux and Android. I thought that this will be also a good occasion
to introduce lockless mechanisms to improve efficiency.
Regards,
Krzysztof
[-- Attachment #1.2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3290 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-04-27 9:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-27 8:59 [PATCH 0/2] GuC logger redesign Krzysztof E. Olinski
2017-04-27 8:59 ` [PATCH 1/2] A lockless Buffering Utility for Concurrency Krzysztof E. Olinski
2017-04-27 8:59 ` [PATCH 2/2] Simplification of guc logger design Krzysztof E. Olinski
2017-04-27 9:05 ` [PATCH 0/2] GuC logger redesign Chris Wilson
2017-04-27 9:22 ` Olinski, Krzysztof E [this message]
2017-04-27 9:53 ` chris
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=1493284929.20321.1.camel@intel.com \
--to=krzysztof.e.olinski@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.