Re: [Mesa-dev] Introducing OpenSWR: High performance software rasterizer

> On Feb 17, 2016, at 7:07 PM, Roland Scheidegger wrote: > > You could use different functions for avx and avx2 code, and plug the > right ones in at runtime, as you can link them both just fine. It just > requires that your code containing avx2 code is in a different

Re: [Mesa-dev] Introducing OpenSWR: High performance software rasterizer

On Thu, Feb 18, 2016 at 02:07:25AM +0100, Roland Scheidegger wrote: > Am 17.02.2016 um 22:09 schrieb Rowley, Timothy O: > >> On Nov 18, 2015, at 12:34 PM, Emil Velikov > >> wrote: I have no objections against > >> getting this merged, although here are a couple of things

Re: [Mesa-dev] Introducing OpenSWR: High performance software rasterizer

Am 17.02.2016 um 22:09 schrieb Rowley, Timothy O: >> On Nov 18, 2015, at 12:34 PM, Emil Velikov >> wrote: I have no objections against >> getting this merged, although here are a couple of things that >> should be sorted. Some of these are just reiteration from others: >

Re: [Mesa-dev] Introducing OpenSWR: High performance software rasterizer

> On Nov 18, 2015, at 12:34 PM, Emil Velikov wrote: > I have no objections against getting this merged, although here are a > couple of things that should be sorted. Some of these are just > reiteration from others: Sorry about the delay responding to this; we’ve been

Re: [Mesa-dev] Introducing OpenSWR: High performance software rasterizer

Hi Tim, I have no objections against getting this merged, although here are a couple of things that should be sorted. Some of these are just reiteration from others: - First and foremost - please base your work against master. Mesa, alike most other open-source projects, tries to keep features

Re: [Mesa-dev] Introducing OpenSWR: High performance software rasterizer

> On Oct 22, 2015, at 4:17 PM, Jose Fonseca wrote: > > They do share a lot already, Mesa, gallium statetracker, and gallivm. If > further development in openswr is planned, it might require to jump through a > few hoops, but I think it's worth to figure out what would

Re: [Mesa-dev] Introducing OpenSWR: High performance software rasterizer

Am 10.11.2015 um 20:36 schrieb Rowley, Timothy O: > >> On Oct 22, 2015, at 4:17 PM, Jose Fonseca wrote: >> >> They do share a lot already, Mesa, gallium statetracker, and gallivm. If >> further development in openswr is planned, it might require to jump through >> a few

Re: [Mesa-dev] Introducing OpenSWR: High performance software rasterizer

On 22/10/15 00:43, Rowley, Timothy O wrote: On Oct 20, 2015, at 5:58 PM, Jose Fonseca wrote: Thanks for the explanations. It's closer now, but still a bit of gap: $ KNOB_MAX_THREADS_PER_CORE=0 ./gloss SWR create screen! This processor supports AVX2. --> numThreads = 3

Re: [Mesa-dev] Introducing OpenSWR: High performance software rasterizer

> On Oct 20, 2015, at 2:03 PM, Roland Scheidegger wrote: > > Certainly looks interesting... > From a high level point of view, seems quite similar to llvmpipe (both > tile based, using llvm for jitting shaders, ...). Of course llvmpipe > isn't well suited for these kind of

Re: [Mesa-dev] Introducing OpenSWR: High performance software rasterizer

Am 22.10.2015 um 00:41 schrieb Rowley, Timothy O: > >> On Oct 20, 2015, at 2:03 PM, Roland Scheidegger wrote: >> >> Certainly looks interesting... >> From a high level point of view, seems quite similar to llvmpipe (both >> tile based, using llvm for jitting shaders, ...). Of

Re: [Mesa-dev] Introducing OpenSWR: High performance software rasterizer

> On Oct 20, 2015, at 5:58 PM, Jose Fonseca wrote: > > Thanks for the explanations. It's closer now, but still a bit of gap: > > $ KNOB_MAX_THREADS_PER_CORE=0 ./gloss > SWR create screen! > This processor supports AVX2. > --> numThreads = 3 > 1102 frames in 5.002 seconds

Re: [Mesa-dev] Introducing OpenSWR: High performance software rasterizer

Am 20.10.2015 um 19:11 schrieb Rowley, Timothy O: > Hi. I'd like to introduce the Mesa3D community to a software project > that we hope to upstream. We're a small team at Intel working on > software defined visualization (http://sdvis.org/), and have > opensource projects in both the raytracing

Re: [Mesa-dev] Introducing OpenSWR: High performance software rasterizer

[re-adding mesa-dev, dropped accidentally] On Tue, Oct 20, 2015 at 1:43 PM, Ilia Mirkin wrote: > On Tue, Oct 20, 2015 at 1:11 PM, Rowley, Timothy O > wrote: >> Does one build work on both AVX and AVX2? >>

Re: [Mesa-dev] Introducing OpenSWR: High performance software rasterizer

> On Oct 20, 2015, at 12:44 PM, Ilia Mirkin wrote: > > On Tue, Oct 20, 2015 at 1:43 PM, Ilia Mirkin wrote: >> On Tue, Oct 20, 2015 at 1:11 PM, Rowley, Timothy O >> wrote: >>> Does one build work on both AVX and AVX2? >>>

[Mesa-dev] Introducing OpenSWR: High performance software rasterizer

Hi. I'd like to introduce the Mesa3D community to a software project that we hope to upstream. We're a small team at Intel working on software defined visualization (http://sdvis.org/), and have opensource projects in both the raytracing (Embree, OSPRay) and rasterization (OpenSWR) realms.

Re: [Mesa-dev] Introducing OpenSWR: High performance software rasterizer

On 20/10/15 18:11, Rowley, Timothy O wrote: Hi. I'd like to introduce the Mesa3D community to a software project that we hope to upstream. We're a small team at Intel working on software defined visualization (http://sdvis.org/), and have opensource projects in both the raytracing (Embree,

Re: [Mesa-dev] Introducing OpenSWR: High performance software rasterizer

On 20/10/15 23:16, Rowley, Timothy O wrote: On Oct 20, 2015, at 4:23 PM, Jose Fonseca wrote: I tried it on my i7-5500U, but I run into two issues: - OpenSWR seems to only use 2 threads (even though my system support 4 threads) - and even when I compensate llvmpipe to

Re: [Mesa-dev] Introducing OpenSWR: High performance software rasterizer

> On Oct 20, 2015, at 4:23 PM, Jose Fonseca wrote: > > I tried it on my i7-5500U, but I run into two issues: > > - OpenSWR seems to only use 2 threads (even though my system support 4 > threads) > > - and even when I compensate llvmpipe to only use 2 rasterizer threads,