On Sun, 18 Oct 2009 01:15:45 - Roman Shaposhnik
wrote:
> On Thu, Oct 15, 2009 at 10:53 AM, Sam Watkins wrote:
> > On Wed, Oct 14, 2009 at 06:50:28PM -0700, Roman Shaposhnik wrote:
> >> > The mention that "... the overhead of cache coherence restricts the ab=
> ility
> >> > to scale up to ev
>> One thing complicating this is that make and its common
>> variants aren't smart enough to handle the case where
>> version control systems regress a file and present an
>> earlier date not newer than the derived object.
>
> See cons/scons.
Thanks for the suggestion. In this project someone ac
On Thu, Oct 15, 2009 at 10:53 AM, Sam Watkins wrote:
> On Wed, Oct 14, 2009 at 06:50:28PM -0700, Roman Shaposhnik wrote:
>> > The mention that "... the overhead of cache coherence restricts the ability
>> > to scale up to even 80 cores" is also eye openeing. If we're at aprox 8
>> > cores today, t
On Fri, Oct 16, 2009 at 5:21 PM, Sam Watkins wrote:
> On Thu, Oct 15, 2009 at 04:21:16PM +0100, roger peppe wrote:
>> BTW it seems the gates quote is false:
>>
>> http://en.wikiquote.org/wiki/Bill_Gates
>
> maybe the Ken quote is false too - hard to believe he's that out of touch
I think the reve
On Sun, Oct 18, 2009 at 12:06 AM, ron minnich wrote:
> the use of qualitative terms such as "embarassingly parallel" often
> leads to confusion.
>
> Scaling can be measured. It can be quantified. Nothing scales forever,
> because at some point you want to get an answer back to a person,
> and/or t
the use of qualitative terms such as "embarassingly parallel" often
leads to confusion.
Scaling can be measured. It can be quantified. Nothing scales forever,
because at some point you want to get an answer back to a person,
and/or the components of the app need to talk to each other. It's
these b
Could be wrong, but I think he's referring to the SPURS Engine:
http://en.wikipedia.org/wiki/SpursEngine
-eric
On Oct 17, 2009, at 4:07 PM, Steve Simon wrote:
I'm a tiny fish, this is the ocean. Nevertheless, I venture: there
are
already Cell-based expansion cards out there for "rea
> I'm a tiny fish, this is the ocean. Nevertheless, I venture: there are
> already Cell-based expansion cards out there for "real-time"
> H.264/VC-1/MPEG-4 AVC encoding. Meaning, 1080p video in, H.264 stream out,
> "real-time."
Interesting, 1080p? you have a link?
-Steve
> One thing complicating this is that make and its common
> variants aren't smart enough to handle the case where
> version control systems regress a file and present an
> earlier date not newer than the derived object.
See cons/scons.
Dave Eckhardt
There is a vast range of applications that cannot
be managed in real time using existing single-core technology.
please name one.
I'm a tiny fish, this is the ocean. Nevertheless, I venture: there are
already Cell-based expansion cards out there for "real-time"
H.264/VC-1/MPEG-4 AVC encoding
My friend Mike and I were talking a while back about Unix init systems
and came to the conclusion that mk's dependency tracking could come in
handy. I decided to implement it a few days ago using plan9port and
thought that some of the folks here might be interested. Although, I
still haven't decide
On Fri, Oct 16, 2009 at 10:03 AM, Sam Watkins wrote:
> On Thu, Oct 15, 2009 at 12:50:48PM +0100, Richard Miller wrote:
>> > It's easy to write good code that will take advantage of arbitrarily many
>> > processors to run faster / smoother, if you have a proper language for the
>> > task.
>>
>> ...
Hello,
is there anyone who could say a few words about their experience with
the lout formatting system and how well it compares to the troff/TeX
suite.
Also, does anybody use it in plan9?
Thanks,
Ruda
13 matches
Mail list logo
