Article: Hot Chips XXI Preview
By: AM (myname4rwt.delete@this.jee.male), October 1, 2009 4:05 am
Room: Moderated Discussions
Jukka Larja (roskakori2006@gmail.com) on 10/1/09 wrote:
---------------------------
>AM (myname4rwt@jee.male) on 9/30/09 wrote:
>---------------------------
>
>> Your example has very little to do with
>> the subject of the discussion you joined.
>
>Yes, and I'm pretty sure I stated that before. I certainly stated it in my last
>message. Do you even read these messages through before you start answering? Or
>do you just prefer to tackle them from beginning to the end in such a small pieces
>that there's bound to be misunderstandings.
>
>The whole three statements thing came from the fact that I thought interpreted
>what you were writing (not to Jouni, but to me) to mean that there is no cost to
>add OoOE to a core[1].
I seriously doubt I said that. Are you sure? I recall I mentioned on several occasions that I don't dispute power and die overheads (have you seen those?).
If this is the whole reason why you keep posting to "correct my misunderstanding", I'd like to see the post+sentence you're talking about.
For me, it was pretty clear, and still is, that there is
>a cost, and OoOE has to bring some benefits to make sense. Whether that cost is
>meaningfull compared to cost X or whether the benefits on workload Y are ten times
>greater than the cost is another discussion.
>
>However, as long as there is a cost, it reflects to clockspeed, if that is the
>only variable you can change. In practise it may not matter, because there are other
>variables and even if it did, absolute clockspeed isn't important anyway.
>
>It doesn't really matter to me whether the cost is in power or somewhere else.
>I thought power was a clear example and chose it.
You chose something that was never a point of disagreement in the prior discussion. And yet you find that someone, and not you!, doesn't get any of it? Superb.
>[1] Not taking into account the cost of more competent engineers or longer design
>cycle. I think those aren't the problem here.
>
>> If you dispute anything of what I said,
>> please point it out and as clearly and
>> concisely as possible so we can
>> concentrate on that w/o wasting time.
>
>I think you stated (or implied or whatever) that implementing OoO has no cost.
>Dont's ask me to show where, that didn't work then and probably won't work now.
No, I don't believe I stated OoO is free. On the contrary, you should be able to find me saying that OoOE needs to be justified, or doesn't contribute to higher performance on certain class of workloads regardless of how well-designed and advanced it is.
>Most likely I just misunderstood you. If you want to further the discussion instead
>of finding someone to blame, just answer as well as possible.
I hope the above answer helps (except links to the posts), so if this is something you were missing or misunderstanding at the outset, what's the meaningful point of your "trying to point out the misunderstanding" posts, let alone any further discussion in the same key?
>> Why change the subject?
>
>Not really sure at this point what subject you are referring to. I think that you
>have been changing the subject the whole time since I got into this discussion,
>or forced me to change it, but I gather you don't agree on that. Which to me means
>that we have a communication problem and for you apparently that I'm some sort of a troll.
>
>> It's not quite clear what you're trying to
>> say here. Do you disagree with anything
>> what I said?
>
>If I interpret what you have said in a suitable context then no, I don't disagree.
>But there's nothing special about that. Language is inaccurate tool. I think I have
>stated before that your facts aren't the problem, just the meaning you assign to
>them (or more accurately, the meaning you assign to facts of other people).
What are those?
>> Yes, so what? Please, state clearly what
>> you're trying to support/dispute using
>> energy argument, because from what you
>> say, the connection with your accusation
>> of me "not getting any of the
>> discussion" is far from obvious.
>
>There is no direct connection. Its about theoretical cost of OoO which came up later.
OK, this was addressed above.
>>> By the way, this isn't (as far as I can see)
>>> not what Jouni was after and not the reason
>>> I got into this discussion. I brought these
>>> up because it seemed you can't see OoOE to
>>> have any negative impact to clock speed, no
>>> matter how theoretical or how unrealistic
>>> (or rather irrelevant) in practise.
>
>I would have appreciated a lot if you would have taken this into account before writing your answer thus far.
>
>> Once again: no, OoOE is not *bound* to have
>> any impact on clock rate. Your line of
>> thinking -- if I understand correctly --
>> that *anything* that increases power
>> consumption must have a negative impact on
>> clock rate,
>
>I think the bound and must may be a problem here. I'm just trying to say that if
>there is a cost and you choose not to pay it in anywhere else, then you have to
>pay it in clockspeed.
No, no, this is a very... well, primitive look. As primitive as Jouni arguing that since 603ev clocked higher than original 603, then it must have had a longer pipeline.
I'm not trying to argue that clockspeed is the only, or best
>or even sensible place to pay the cost.
>
>I think Jouni's argument is better one since he at least is talking about propagation
>distances and added stages. I'm a lot farther from practical issues.
Thank you for the better-argument part, for I believe the matter of propagation delays across larger cores was in fact accentuated by me (along with large-cache example which makes it simple to understand).
>> is ridiculously far from theory, from practice,
>
>Well, with "bound" and "must" it surely is, but I never tried to argue that.
>
>> and from what was being discussed in the thread
>> you jumped in in the first place for quite
>> clear reasons I gave you clues to. So, do you
>> understand why or do you want a more detailed
>> explanation?
>
>Well, I didn't even mean to get to technical argument and I certainly don't see
>why I would even try to support Jouni's point if you keep interpreting it on your terms.
I'm talking about your own argument.
>> And why do you think clock rate is the
>> only free variable to adjust, to begin
>> with?
>
>Because I chose it to be. This was my example and my three statements remember?
>I didn't expect to get them clear enough on the first time I wrote them. I thought
>we could discuss them to clear out what I was meaning and see whether we actually
>have an argument over facts or just a misunderstanding of the issue.
OK, since I answered your question re. OoOE costs above, I gather it's up to you now to conclude whether misunderstanding took place or not.
>> I refer to the discussion that was taking
>> place. If you're really disputing something
>> from that, you shouldn't impose your own
>> context in the first place.
>
>(I'm not quite sure how well I understand the finer meaning of word impose, but
>anyway...) It didn't seem like you were considering other possible context yourself.
>Neither did it seem like you and Jouni were discussing in the same context or that
>you were going to stop anytime soon. I also think that you weren't addressing the
>really relevant aspects of what Jouni was saying, but mostly just getting stuck with less relevant mistakes.
>
>But this is my just how I read the discussion. I don't think there's any absolute truth to be found.
I think that if you're really trying to be helpful, you should instead refer to posts and point out his "really relevant" aspects etc. That would be more useful.
>> Then I have a question: does your "everething
>> else being equal" include die space or not,
>> and why?
>
>As we are talking about _adding_ OoO to a chip, no, it doesn't. Unless there is
>something that you clearly remove from an in-order design when adding OoO, then we need to talk about it.
>
>(By the way, I have a horrible feeling the some day someone is going to take these
>words out of context and I'm going to look like a total idiot :) .)
You don't need to wait until someday, mate. I'm asking you today: what's the logic behind fixing the power envelope ("not a nanowatt more", IIRC), but allowing the die space?
>> Excuse me, but why does the "wrong" or
>> "different" context apply to one and not
>> the other side? Who are you to decide,
>> let me ask, even if that were true?
>
>Well, different obviously applys to both sides (that's by definition). I used the
>word wrong for the same reason I chose to reply to you. I think Jouni tried to make
>his context known and you were ignoring it, so that made you a logical candidate
>for my answer. Wrong is probably a bad word because it has emotional baggage, but
>it's not like I was going to step in if I thought you were right, right?
Then I'd like to see what exactly you mean as requested above.
>> Let's see. You jump in a thread w/o caring to
>> read it through, as it turns out,
>
>I've said that I don't care to read the thread again. I have read pretty much every
>message posted to this forum since I started visiting it (I have skipped parts of
>political discussions and some messages which I couldn't comprehend in grammatical sense).
>
>Reading the whole thread, or even just the subthread from Jouni's first post, again
>would take me hours. It isn't something I'm going to do just to please you.
Not to please me. If you read the thread indeed, how can it be unknown to you that I never disputed power and die costs etc.?
>> esp. considering you're changing the
>> original context?
>
>From my point of view I was forced to seek a more simple example because you didn't
>seem to understand me. After that point we were far from what you were talking with
>Jouni about. I don't think that change of subject was in any ways deceitful or me
>trying to prove Jouni's arguments with some obscure examples.
Deceitful or not, it's of no help to your accusations of your claims of "not getting the discussion".
And it was brought up when I requested some clarity on the obvious contradiction in your own text (smth. about the waste in OoOE). Remember?
>> Well, are you sure you're the one who
>> understands properly everything?
>
>No. I have stated that. If I was, we could have perhaps not a meaningful discussion
>but at least a discussion on equal footing. As long as you think you're absolutely
>right and I'm willing to admit that I'm may not be, we're just stuck dancing aroung each other.
My questions to Jouni (and yourself) when I couldn't really decypher what was said, and complete lack of such questions on his part (or yours, for that matter, when you jumped in claiming someone doesn't understand instead of clarifying) should give a way more meaningful indication as to who tends to think he's right, then whatever one can say in his defence.
>> If that's really the case, then why do
>> you start with insults rather than
>> simple pointing out of
>> misunderstandings?
>
>I didn't mean to insult. I meant to make a strong, perhaps somewhat exaggerated
>statement and forgot all my good advice about communication especially between people
>of different languages and cultures. I didn't mean to be totally polite either,
>but what I wrote most likely was stronger than I had in mind.
>
>Apologies for that.
IIRC, your statement was something about theoretical standpoint. As such, it's an empty point as long as there's no theoretical substantiation -- and I haven't seen one. Perhaps I shouldn't have even expected to see anything from a person who seriously suggests that higher clockrate in 603ev must be coming from a longer pipeline or that someone else's TTA/systolic array-type arch won't work.
>>> By the way, you are talking about
>>> Hans de Vries, right?
>>
>> Yes. Don't recall any other Hans
>> posting here.
>
>Neither do I, but I'm not quite arrogant enough to think my memory's perfect. And
>it was easier to ask than to go searching not to find :) .
>
>> This is not a matter of thinking/context,
>> just a clear example of how he developed
>> his argument.
>
>I think Jouni was mostly reacting to what you said, whether it was particularly
>relevant to his argument or not. I don't think we can get anywhere analyzing what
>he said. He and I share cultural and lingual background, so I don't think I'm going
>to take your interpretations over mine just because.
No need to analyze or interpret, just take it for what it is.
>(For example, you didn't seem to understand Jouni's reference to debating culture.
>Now I don't know whether he was right to make that reference or not, but I do understand
>why he made it. I'm also not in any way surprised if you don't. It's one of the
>issues that often causes problems in communication between Finns and Europians and North Americans.)
What ref. is it?
>> It didnt't lead anywhere because with that
>> you're just changing the problem. Why
>> would you do it?
>
>You assume I changed the problem when I posted a different example, but fail to
>see that the misunderstanding had already happened at that point. I didn't change
>the problem, I reformulated it in simpler form. If that simpler form shows that
>we agree, then there's no need to discuss the original, more complicated problem.
>We can simply conclude that I misunderstood you.
>
>And just to be clear, the problem discussed here still isn't the one you and Jouni were discussing.
So, are you just exercising in debating?
>> The way it goes from your side, there's
>> very little point really. If you set out
>> to dispute something of what was said,
>> you should begin with pointing it out.
>
>I'm not sure whether dispute is a right word, but what I wanted to dispute was
>your interpretation of the point Jouni was trying to make.
Then -- in case you're really trying to help communication -- I look forward to seeing above-requested examples.
>> The "three basic truths" hardly count as
>> theory, this is just a specific context
>> (same power budget) you have chosen to
>> show how someone else was "wrong" or
>> "misunderstanding".
>
>Well, I was trying to show that I had misunderstood. Of course, before that you
>probably misunderstood something I wrote, but that may simply be because I had formulated
>it badly, assumed a context that wasn't as clear as I thought and so on.
>
>The thing is, I expected "the three basic truths" discussion to quickly get to
>a point where I write that I just misunderstood what you meant, no need to argue this anymore.
Well, if you feel you misunderstood me, what's the point in continuing this discussion?
In case you want to see my posts where I said this or that, but don't want to spend your time searching them, I can spend *my* time if it will be enough. I just suspect that even this will not be enough and will likely result in yet another post from you how I seem to not respect context, not listen to what others say etc.
>> Rudeness is one thing, another thing is you
>> say that someone doesn't get something
>> when apparently you didn't even care to
>> read the discussion in full to understand
>> where it comes from.
>
>I don't know where you got the idea I haven't read the whole discussion, but it is wrong.
>
>> It's simply surprizing and very
>> frustrating to see such cheap shots
>> from someone with self-proclaimed
>> academic background and admiration
>> of theory.
>
>I'm writing with my real name shown. If you want to confirm my academic background, you can do it.
>
>And since you like to flaunt my admiration of theory around I should probably add
>that I admire practise as well. (Actually, there are very few things I don't admire.)
>You can add that to your oh-I-just-mentioned-it-because-you-brought-it-up list of characterizations of me.
Done.
>> That's exactly why he got from me a fair and
>> well-deserved share of examples. Starting to
>> get it now?
>
>Well, no. I still just see the same argument that you know what he meant, and my
>interpretation (and as far as I can see, Jouni's own) are just changing the argument.
>Like this was some sort of a contest where your job is to show that we are trying to cheat.
I gave you already a short list of his fantastic arguments, if there's anything I forgot to mention, it's in the thread.
>> Actually, I never tried to switch the
>> context.
>
>I can believe that. Can you believe that neither was I? The context got screwed
>up. It happens all the time. Trying to assign a blame is pointless.
I think you admitted that the context you introduced differed significantly. No?
>>>> Yes, and one doesn't have to look far: in
>>>> this very thread you can find numerous
>>>> examples where communication doesn't seem
>>>> to work or words like "first" are
>>>> mistakenly interpreted as "last". :)
>>>
>>> Should I interpret this to mean that you
>>> don't think understanding can be an issue
>>> here :) .
>>
>> I suggest you should interpret it as the
>> smile suggests -- I started putting them
>> more often to help you get the meaning
>> right. To put it even more clearly for
>> you, attempts at defending one's argument
>> with made-up facts (Jouni) or theory
>> (you) is hardly a matter of
>> misunderstanding. Word "trolling" comes
>> to mind.
>
>Making something up is different from making a mistake (for example, remembering
>incorrectly). My point here was that what Jouni said about Prescott wasn't that
>relevant to his point (thus the mistake isn't that relevant), and you only think
>it is because you two were argueing in different context.
Prescott is just a particular (but telling) example. The context -- no, it's you who thinks of different context etc.
>> No, what you're actually doing is trying
>> to switch the context of original
>> discussion.
>
>You don't need to repeat yourself. It just wears me down trying to decide where
>to write my answers and trying to keep up whether I have addressed all relevant issues.
I don't try to repeat myself, it comes naturally.
>> No, I'm talking about the discussion you
>> jumped in w/o caring to read it. It was
>> me asking Jouni to clarify what he said.
>
>I think Jouni was doing pretty good job in general. He just shouldn't have addressed the details that weren't relevant.
>
>But what do I know. Perhaps I interpreted Jouni all wrong.
Or just defended your friend not caring much about the subject and essence of the discussion?
>>>>> What I have done is spent hours talking to
>>>>> students and working out wordings to make
>>>>> exercises (both in Finnish and English) as
>>>>> unambiguous as ever. Only to see someone
>>>>> completely ignore the context,
>>>>> misunderstand the point and come yelling
>>>>> to us that we are idiots.
>>>>
>>>> Well, it appears it only shows that careful
>>>> working out the wordings was a waste. :)
>>>> Someone ignored the context anyway, while
>>>> others probably wouldn't need the extra
>>>> work you put in to understand things
>>>> correctly (or just ask if in doubt).
>>>
>>> Funny, but your making assumptions out of
>>> context again :) (context I didn't give,
>>> so no wonder. People usually have very
>>> weird ideas about teaching. Often very
>>> idealistic and simplyfied, ignoring the
>>> practise. Many ideas that are
>>> theoretically speaking sound, simply don't
>>> work /selfirony).
>>
>> I didn't assume anything for what was said,
>> certainly not #students as you suggest
>> below. Just made a direct observation that
>> there were people for whom extra work was
>> unneeded and could have well been
>> unnecessary for others.
>
>Yeah, but that observation makes no sense for me in my context whatsoever. Given
>large enough body of students, it is statisticly speaking certain that someone won't
>understand no matter how hard you try to explain, and that someone will understand
>(or at least guess correctly), no matter how much you muddy the assignment.
>
>You are stating the obvious, after you have made an incorrect statement about waste.
>I took that to mean you used that latter statement to justify the first. That you
>thought the hours used to clear up the assignment were wasted. That only makes sense
>if you think number of students was small and thus the one complainer was significant
>part of them and thus somehow showed that we had been wasting time improving the excercise.
>
>Sure, there was a smiley of yours, but so there was a smiley of mine. Just to balance
>things out. If you were just stretching the truth for humorous tone, just read my answer in a same way.
>
>> Yet another example of how you prefer to
>> blame others for "out-of-context
>> assumptions" when it's not even true.
>
>I did say that you couldn't have known the context, because I didn't state it,
>I had a smiley there and even a rant marked with /selfirony. I don't see what more
>I could do to state that I don't blame you.
>
>Simply put, you were totally wrong and I assumed it was because I didn't specify
>very important part of the context, the number of students that is. Of course, there are other possible reasons.
Like the whole example was meant to yield a response and then show how easily I can misunderstand what was "really" meant? Ah, geddit now.
>-JLarja
---------------------------
>AM (myname4rwt@jee.male) on 9/30/09 wrote:
>---------------------------
>
>> Your example has very little to do with
>> the subject of the discussion you joined.
>
>Yes, and I'm pretty sure I stated that before. I certainly stated it in my last
>message. Do you even read these messages through before you start answering? Or
>do you just prefer to tackle them from beginning to the end in such a small pieces
>that there's bound to be misunderstandings.
>
>The whole three statements thing came from the fact that I thought interpreted
>what you were writing (not to Jouni, but to me) to mean that there is no cost to
>add OoOE to a core[1].
I seriously doubt I said that. Are you sure? I recall I mentioned on several occasions that I don't dispute power and die overheads (have you seen those?).
If this is the whole reason why you keep posting to "correct my misunderstanding", I'd like to see the post+sentence you're talking about.
For me, it was pretty clear, and still is, that there is
>a cost, and OoOE has to bring some benefits to make sense. Whether that cost is
>meaningfull compared to cost X or whether the benefits on workload Y are ten times
>greater than the cost is another discussion.
>
>However, as long as there is a cost, it reflects to clockspeed, if that is the
>only variable you can change. In practise it may not matter, because there are other
>variables and even if it did, absolute clockspeed isn't important anyway.
>
>It doesn't really matter to me whether the cost is in power or somewhere else.
>I thought power was a clear example and chose it.
You chose something that was never a point of disagreement in the prior discussion. And yet you find that someone, and not you!, doesn't get any of it? Superb.
>[1] Not taking into account the cost of more competent engineers or longer design
>cycle. I think those aren't the problem here.
>
>> If you dispute anything of what I said,
>> please point it out and as clearly and
>> concisely as possible so we can
>> concentrate on that w/o wasting time.
>
>I think you stated (or implied or whatever) that implementing OoO has no cost.
>Dont's ask me to show where, that didn't work then and probably won't work now.
No, I don't believe I stated OoO is free. On the contrary, you should be able to find me saying that OoOE needs to be justified, or doesn't contribute to higher performance on certain class of workloads regardless of how well-designed and advanced it is.
>Most likely I just misunderstood you. If you want to further the discussion instead
>of finding someone to blame, just answer as well as possible.
I hope the above answer helps (except links to the posts), so if this is something you were missing or misunderstanding at the outset, what's the meaningful point of your "trying to point out the misunderstanding" posts, let alone any further discussion in the same key?
>> Why change the subject?
>
>Not really sure at this point what subject you are referring to. I think that you
>have been changing the subject the whole time since I got into this discussion,
>or forced me to change it, but I gather you don't agree on that. Which to me means
>that we have a communication problem and for you apparently that I'm some sort of a troll.
>
>> It's not quite clear what you're trying to
>> say here. Do you disagree with anything
>> what I said?
>
>If I interpret what you have said in a suitable context then no, I don't disagree.
>But there's nothing special about that. Language is inaccurate tool. I think I have
>stated before that your facts aren't the problem, just the meaning you assign to
>them (or more accurately, the meaning you assign to facts of other people).
What are those?
>> Yes, so what? Please, state clearly what
>> you're trying to support/dispute using
>> energy argument, because from what you
>> say, the connection with your accusation
>> of me "not getting any of the
>> discussion" is far from obvious.
>
>There is no direct connection. Its about theoretical cost of OoO which came up later.
OK, this was addressed above.
>>> By the way, this isn't (as far as I can see)
>>> not what Jouni was after and not the reason
>>> I got into this discussion. I brought these
>>> up because it seemed you can't see OoOE to
>>> have any negative impact to clock speed, no
>>> matter how theoretical or how unrealistic
>>> (or rather irrelevant) in practise.
>
>I would have appreciated a lot if you would have taken this into account before writing your answer thus far.
>
>> Once again: no, OoOE is not *bound* to have
>> any impact on clock rate. Your line of
>> thinking -- if I understand correctly --
>> that *anything* that increases power
>> consumption must have a negative impact on
>> clock rate,
>
>I think the bound and must may be a problem here. I'm just trying to say that if
>there is a cost and you choose not to pay it in anywhere else, then you have to
>pay it in clockspeed.
No, no, this is a very... well, primitive look. As primitive as Jouni arguing that since 603ev clocked higher than original 603, then it must have had a longer pipeline.
I'm not trying to argue that clockspeed is the only, or best
>or even sensible place to pay the cost.
>
>I think Jouni's argument is better one since he at least is talking about propagation
>distances and added stages. I'm a lot farther from practical issues.
Thank you for the better-argument part, for I believe the matter of propagation delays across larger cores was in fact accentuated by me (along with large-cache example which makes it simple to understand).
>> is ridiculously far from theory, from practice,
>
>Well, with "bound" and "must" it surely is, but I never tried to argue that.
>
>> and from what was being discussed in the thread
>> you jumped in in the first place for quite
>> clear reasons I gave you clues to. So, do you
>> understand why or do you want a more detailed
>> explanation?
>
>Well, I didn't even mean to get to technical argument and I certainly don't see
>why I would even try to support Jouni's point if you keep interpreting it on your terms.
I'm talking about your own argument.
>> And why do you think clock rate is the
>> only free variable to adjust, to begin
>> with?
>
>Because I chose it to be. This was my example and my three statements remember?
>I didn't expect to get them clear enough on the first time I wrote them. I thought
>we could discuss them to clear out what I was meaning and see whether we actually
>have an argument over facts or just a misunderstanding of the issue.
OK, since I answered your question re. OoOE costs above, I gather it's up to you now to conclude whether misunderstanding took place or not.
>> I refer to the discussion that was taking
>> place. If you're really disputing something
>> from that, you shouldn't impose your own
>> context in the first place.
>
>(I'm not quite sure how well I understand the finer meaning of word impose, but
>anyway...) It didn't seem like you were considering other possible context yourself.
>Neither did it seem like you and Jouni were discussing in the same context or that
>you were going to stop anytime soon. I also think that you weren't addressing the
>really relevant aspects of what Jouni was saying, but mostly just getting stuck with less relevant mistakes.
>
>But this is my just how I read the discussion. I don't think there's any absolute truth to be found.
I think that if you're really trying to be helpful, you should instead refer to posts and point out his "really relevant" aspects etc. That would be more useful.
>> Then I have a question: does your "everething
>> else being equal" include die space or not,
>> and why?
>
>As we are talking about _adding_ OoO to a chip, no, it doesn't. Unless there is
>something that you clearly remove from an in-order design when adding OoO, then we need to talk about it.
>
>(By the way, I have a horrible feeling the some day someone is going to take these
>words out of context and I'm going to look like a total idiot :) .)
You don't need to wait until someday, mate. I'm asking you today: what's the logic behind fixing the power envelope ("not a nanowatt more", IIRC), but allowing the die space?
>> Excuse me, but why does the "wrong" or
>> "different" context apply to one and not
>> the other side? Who are you to decide,
>> let me ask, even if that were true?
>
>Well, different obviously applys to both sides (that's by definition). I used the
>word wrong for the same reason I chose to reply to you. I think Jouni tried to make
>his context known and you were ignoring it, so that made you a logical candidate
>for my answer. Wrong is probably a bad word because it has emotional baggage, but
>it's not like I was going to step in if I thought you were right, right?
Then I'd like to see what exactly you mean as requested above.
>> Let's see. You jump in a thread w/o caring to
>> read it through, as it turns out,
>
>I've said that I don't care to read the thread again. I have read pretty much every
>message posted to this forum since I started visiting it (I have skipped parts of
>political discussions and some messages which I couldn't comprehend in grammatical sense).
>
>Reading the whole thread, or even just the subthread from Jouni's first post, again
>would take me hours. It isn't something I'm going to do just to please you.
Not to please me. If you read the thread indeed, how can it be unknown to you that I never disputed power and die costs etc.?
>> esp. considering you're changing the
>> original context?
>
>From my point of view I was forced to seek a more simple example because you didn't
>seem to understand me. After that point we were far from what you were talking with
>Jouni about. I don't think that change of subject was in any ways deceitful or me
>trying to prove Jouni's arguments with some obscure examples.
Deceitful or not, it's of no help to your accusations of your claims of "not getting the discussion".
And it was brought up when I requested some clarity on the obvious contradiction in your own text (smth. about the waste in OoOE). Remember?
>> Well, are you sure you're the one who
>> understands properly everything?
>
>No. I have stated that. If I was, we could have perhaps not a meaningful discussion
>but at least a discussion on equal footing. As long as you think you're absolutely
>right and I'm willing to admit that I'm may not be, we're just stuck dancing aroung each other.
My questions to Jouni (and yourself) when I couldn't really decypher what was said, and complete lack of such questions on his part (or yours, for that matter, when you jumped in claiming someone doesn't understand instead of clarifying) should give a way more meaningful indication as to who tends to think he's right, then whatever one can say in his defence.
>> If that's really the case, then why do
>> you start with insults rather than
>> simple pointing out of
>> misunderstandings?
>
>I didn't mean to insult. I meant to make a strong, perhaps somewhat exaggerated
>statement and forgot all my good advice about communication especially between people
>of different languages and cultures. I didn't mean to be totally polite either,
>but what I wrote most likely was stronger than I had in mind.
>
>Apologies for that.
IIRC, your statement was something about theoretical standpoint. As such, it's an empty point as long as there's no theoretical substantiation -- and I haven't seen one. Perhaps I shouldn't have even expected to see anything from a person who seriously suggests that higher clockrate in 603ev must be coming from a longer pipeline or that someone else's TTA/systolic array-type arch won't work.
>>> By the way, you are talking about
>>> Hans de Vries, right?
>>
>> Yes. Don't recall any other Hans
>> posting here.
>
>Neither do I, but I'm not quite arrogant enough to think my memory's perfect. And
>it was easier to ask than to go searching not to find :) .
>
>> This is not a matter of thinking/context,
>> just a clear example of how he developed
>> his argument.
>
>I think Jouni was mostly reacting to what you said, whether it was particularly
>relevant to his argument or not. I don't think we can get anywhere analyzing what
>he said. He and I share cultural and lingual background, so I don't think I'm going
>to take your interpretations over mine just because.
No need to analyze or interpret, just take it for what it is.
>(For example, you didn't seem to understand Jouni's reference to debating culture.
>Now I don't know whether he was right to make that reference or not, but I do understand
>why he made it. I'm also not in any way surprised if you don't. It's one of the
>issues that often causes problems in communication between Finns and Europians and North Americans.)
What ref. is it?
>> It didnt't lead anywhere because with that
>> you're just changing the problem. Why
>> would you do it?
>
>You assume I changed the problem when I posted a different example, but fail to
>see that the misunderstanding had already happened at that point. I didn't change
>the problem, I reformulated it in simpler form. If that simpler form shows that
>we agree, then there's no need to discuss the original, more complicated problem.
>We can simply conclude that I misunderstood you.
>
>And just to be clear, the problem discussed here still isn't the one you and Jouni were discussing.
So, are you just exercising in debating?
>> The way it goes from your side, there's
>> very little point really. If you set out
>> to dispute something of what was said,
>> you should begin with pointing it out.
>
>I'm not sure whether dispute is a right word, but what I wanted to dispute was
>your interpretation of the point Jouni was trying to make.
Then -- in case you're really trying to help communication -- I look forward to seeing above-requested examples.
>> The "three basic truths" hardly count as
>> theory, this is just a specific context
>> (same power budget) you have chosen to
>> show how someone else was "wrong" or
>> "misunderstanding".
>
>Well, I was trying to show that I had misunderstood. Of course, before that you
>probably misunderstood something I wrote, but that may simply be because I had formulated
>it badly, assumed a context that wasn't as clear as I thought and so on.
>
>The thing is, I expected "the three basic truths" discussion to quickly get to
>a point where I write that I just misunderstood what you meant, no need to argue this anymore.
Well, if you feel you misunderstood me, what's the point in continuing this discussion?
In case you want to see my posts where I said this or that, but don't want to spend your time searching them, I can spend *my* time if it will be enough. I just suspect that even this will not be enough and will likely result in yet another post from you how I seem to not respect context, not listen to what others say etc.
>> Rudeness is one thing, another thing is you
>> say that someone doesn't get something
>> when apparently you didn't even care to
>> read the discussion in full to understand
>> where it comes from.
>
>I don't know where you got the idea I haven't read the whole discussion, but it is wrong.
>
>> It's simply surprizing and very
>> frustrating to see such cheap shots
>> from someone with self-proclaimed
>> academic background and admiration
>> of theory.
>
>I'm writing with my real name shown. If you want to confirm my academic background, you can do it.
>
>And since you like to flaunt my admiration of theory around I should probably add
>that I admire practise as well. (Actually, there are very few things I don't admire.)
>You can add that to your oh-I-just-mentioned-it-because-you-brought-it-up list of characterizations of me.
Done.
>> That's exactly why he got from me a fair and
>> well-deserved share of examples. Starting to
>> get it now?
>
>Well, no. I still just see the same argument that you know what he meant, and my
>interpretation (and as far as I can see, Jouni's own) are just changing the argument.
>Like this was some sort of a contest where your job is to show that we are trying to cheat.
I gave you already a short list of his fantastic arguments, if there's anything I forgot to mention, it's in the thread.
>> Actually, I never tried to switch the
>> context.
>
>I can believe that. Can you believe that neither was I? The context got screwed
>up. It happens all the time. Trying to assign a blame is pointless.
I think you admitted that the context you introduced differed significantly. No?
>>>> Yes, and one doesn't have to look far: in
>>>> this very thread you can find numerous
>>>> examples where communication doesn't seem
>>>> to work or words like "first" are
>>>> mistakenly interpreted as "last". :)
>>>
>>> Should I interpret this to mean that you
>>> don't think understanding can be an issue
>>> here :) .
>>
>> I suggest you should interpret it as the
>> smile suggests -- I started putting them
>> more often to help you get the meaning
>> right. To put it even more clearly for
>> you, attempts at defending one's argument
>> with made-up facts (Jouni) or theory
>> (you) is hardly a matter of
>> misunderstanding. Word "trolling" comes
>> to mind.
>
>Making something up is different from making a mistake (for example, remembering
>incorrectly). My point here was that what Jouni said about Prescott wasn't that
>relevant to his point (thus the mistake isn't that relevant), and you only think
>it is because you two were argueing in different context.
Prescott is just a particular (but telling) example. The context -- no, it's you who thinks of different context etc.
>> No, what you're actually doing is trying
>> to switch the context of original
>> discussion.
>
>You don't need to repeat yourself. It just wears me down trying to decide where
>to write my answers and trying to keep up whether I have addressed all relevant issues.
I don't try to repeat myself, it comes naturally.
>> No, I'm talking about the discussion you
>> jumped in w/o caring to read it. It was
>> me asking Jouni to clarify what he said.
>
>I think Jouni was doing pretty good job in general. He just shouldn't have addressed the details that weren't relevant.
>
>But what do I know. Perhaps I interpreted Jouni all wrong.
Or just defended your friend not caring much about the subject and essence of the discussion?
>>>>> What I have done is spent hours talking to
>>>>> students and working out wordings to make
>>>>> exercises (both in Finnish and English) as
>>>>> unambiguous as ever. Only to see someone
>>>>> completely ignore the context,
>>>>> misunderstand the point and come yelling
>>>>> to us that we are idiots.
>>>>
>>>> Well, it appears it only shows that careful
>>>> working out the wordings was a waste. :)
>>>> Someone ignored the context anyway, while
>>>> others probably wouldn't need the extra
>>>> work you put in to understand things
>>>> correctly (or just ask if in doubt).
>>>
>>> Funny, but your making assumptions out of
>>> context again :) (context I didn't give,
>>> so no wonder. People usually have very
>>> weird ideas about teaching. Often very
>>> idealistic and simplyfied, ignoring the
>>> practise. Many ideas that are
>>> theoretically speaking sound, simply don't
>>> work /selfirony).
>>
>> I didn't assume anything for what was said,
>> certainly not #students as you suggest
>> below. Just made a direct observation that
>> there were people for whom extra work was
>> unneeded and could have well been
>> unnecessary for others.
>
>Yeah, but that observation makes no sense for me in my context whatsoever. Given
>large enough body of students, it is statisticly speaking certain that someone won't
>understand no matter how hard you try to explain, and that someone will understand
>(or at least guess correctly), no matter how much you muddy the assignment.
>
>You are stating the obvious, after you have made an incorrect statement about waste.
>I took that to mean you used that latter statement to justify the first. That you
>thought the hours used to clear up the assignment were wasted. That only makes sense
>if you think number of students was small and thus the one complainer was significant
>part of them and thus somehow showed that we had been wasting time improving the excercise.
>
>Sure, there was a smiley of yours, but so there was a smiley of mine. Just to balance
>things out. If you were just stretching the truth for humorous tone, just read my answer in a same way.
>
>> Yet another example of how you prefer to
>> blame others for "out-of-context
>> assumptions" when it's not even true.
>
>I did say that you couldn't have known the context, because I didn't state it,
>I had a smiley there and even a rant marked with /selfirony. I don't see what more
>I could do to state that I don't blame you.
>
>Simply put, you were totally wrong and I assumed it was because I didn't specify
>very important part of the context, the number of students that is. Of course, there are other possible reasons.
Like the whole example was meant to yield a response and then show how easily I can misunderstand what was "really" meant? Ah, geddit now.
>-JLarja
Topic | Posted By | Date |
---|---|---|
Hot Chips XXI Preview online | David Kanter | 2009/08/12 02:55 PM |
Hot Chips XXI Preview online | Groo | 2009/08/12 05:27 PM |
Hot Chips XXI Preview online | David Kanter | 2009/08/12 06:17 PM |
recent POWER7 info. from IBM | M.Isobe | 2009/08/16 02:04 AM |
Hot Chips XXI Preview online | slacker | 2009/08/12 08:11 PM |
Attending hot chips | David Kanter | 2009/08/12 08:53 PM |
Power7 vs. single threaded performance and licensing | Daniel Bizó | 2009/08/13 12:05 AM |
Power7 vs. single threaded performance and licensing | Wes Felter | 2009/08/13 11:17 AM |
Power7 vs. single threaded performance and licensing | anon | 2009/08/13 03:25 PM |
Power7 vs. single threaded performance and licensing | Linus Torvalds | 2009/08/13 03:48 PM |
How much IPC | E | 2009/08/14 01:16 AM |
How much IPC | hobold | 2009/08/14 03:03 AM |
How much IPC | a reader | 2009/08/15 10:26 AM |
How much IPC | hobold | 2009/08/15 10:58 AM |
How much IPC | Linus Torvalds | 2009/08/15 12:09 PM |
How much IPC | hobold | 2009/08/15 12:45 PM |
How much IPC | Euronymous | 2009/08/15 01:41 PM |
How much IPC | ? | 2009/08/16 01:13 AM |
How much IPC | Anonymous | 2009/08/16 02:07 AM |
How much IPC | ? | 2009/08/16 03:49 AM |
How much IPC | EduardoS | 2009/08/16 07:04 AM |
How much IPC | Anonymous | 2009/08/16 05:26 PM |
How much IPC | Linus Torvalds | 2009/08/16 07:49 AM |
How much IPC | ? | 2009/08/16 09:32 AM |
How much IPC | EduardoS | 2009/08/16 07:09 AM |
How much IPC | Linus Torvalds | 2009/08/16 08:12 AM |
How much IPC | a reader | 2009/08/16 11:41 AM |
How much IPC | Linus Torvalds | 2009/08/16 12:21 PM |
How much IPC | none | 2009/08/16 01:30 PM |
How much IPC | ? | 2009/08/16 11:32 PM |
How much IPC | ? | 2009/08/17 12:09 AM |
How much IPC | none | 2009/08/17 02:29 AM |
How much IPC | ? | 2009/08/17 05:25 AM |
Speculation and waste | David Kanter | 2009/08/17 10:03 AM |
Speculation and waste | ? | 2009/08/18 11:59 AM |
Speculation and waste | David Kanter | 2009/08/18 12:22 PM |
Speculation and waste | anon | 2009/08/19 02:52 AM |
Speculation and waste | TruePath | 2009/09/27 06:23 AM |
How much IPC | none | 2009/08/18 01:55 AM |
How much IPC | anon | 2009/08/18 02:27 AM |
How much IPC | anon | 2009/08/16 10:05 PM |
How much IPC | Linus Torvalds | 2009/08/17 10:17 AM |
How much IPC | _Arthur | 2009/08/17 03:23 PM |
How much IPC | David Kanter | 2009/08/17 03:38 PM |
How much IPC | Michael S | 2009/08/17 03:39 PM |
How much IPC | David Kanter | 2009/08/17 03:48 PM |
How much IPC | Michael S | 2009/08/17 05:03 PM |
How much IPC | _Arthur | 2009/08/17 05:33 PM |
How much IPC | Michael S | 2009/08/17 05:56 PM |
How much IPC | _Arthur | 2009/08/17 08:48 PM |
How much IPC | Michael S | 2009/08/18 03:07 AM |
limits of sorting | hobold | 2009/08/18 04:26 AM |
limits of sorting | Michael S | 2009/08/18 05:26 AM |
limits of sorting | _Arthur | 2009/08/18 06:03 AM |
limits of sorting | Richard Cownie | 2009/08/18 06:32 AM |
limits of sorting | Michael S | 2009/08/18 07:17 AM |
limits of sorting | Richard Cownie | 2009/08/18 08:22 AM |
limits of sorting | _Arthur | 2009/08/18 08:57 AM |
limits of sorting | Richard Cownie | 2009/08/18 09:30 AM |
limits of sorting | Richard Cownie | 2009/08/18 09:45 AM |
limits of sorting | Michael S | 2009/08/18 09:50 AM |
limits of sorting | Richard Cownie | 2009/08/18 10:09 AM |
limits of sorting | Michael S | 2009/08/18 10:33 AM |
limits of sorting | Richard Cownie | 2009/08/18 10:53 AM |
limits of sorting | Michael S | 2009/08/18 11:28 AM |
limits of sorting | Richard Cownie | 2009/08/18 12:01 PM |
limits of sorting | JasonB | 2009/08/18 06:40 PM |
limits of sorting | Richard Cownie | 2009/08/18 07:22 PM |
You work on EDA right Richard? | David Kanter | 2009/08/18 07:49 PM |
You work on EDA right Richard? | Richard Cownie | 2009/08/19 05:56 AM |
You work on EDA right Richard? | David Kanter | 2009/08/19 08:26 AM |
You work on EDA right Richard? | Richard Cownie | 2009/08/19 08:47 AM |
You work on EDA right Richard? | slacker | 2009/08/19 09:52 AM |
You work on EDA right Richard? | Richard Cownie | 2009/08/19 10:10 AM |
You work on EDA right Richard? | slacker | 2009/08/19 11:36 PM |
You work on EDA right Richard? | slacker | 2009/08/19 11:45 PM |
You work on EDA right Richard? | Richard Cownie | 2009/08/20 05:28 AM |
You work on EDA right Richard? | slacker | 2009/08/20 06:32 AM |
You work on EDA right Richard? | Aaron Spink | 2009/08/20 12:08 AM |
You work on EDA right Richard? | Rob Thorpe | 2009/08/20 08:31 AM |
You work on EDA right Richard? | David Kanter | 2009/08/20 09:58 AM |
You work on EDA right Richard? | Rob Thorpe | 2009/08/20 04:10 PM |
limits of sorting | rwessel | 2009/08/18 07:56 PM |
limits of sorting | JasonB | 2009/08/18 11:11 PM |
limits of sorting | JasonB | 2009/08/18 11:25 PM |
limits of sorting | Richard Cownie | 2009/08/19 06:32 AM |
limits of sorting | Rob Thorpe | 2009/08/19 07:12 AM |
limits of sorting | Richard Cownie | 2009/08/19 07:46 AM |
limits of sorting | JasonB | 2009/08/19 08:43 PM |
limits of sorting | Richard Cownie | 2009/08/20 07:47 AM |
limits of sorting | JasonB | 2009/08/20 08:20 PM |
limits of sorting | Richard Cownie | 2009/08/20 11:12 PM |
limits of sorting | JasonB | 2009/08/21 02:08 AM |
limits of sorting | Richard Cownie | 2009/08/21 05:15 AM |
limits of sorting | JasonB | 2009/08/22 06:24 PM |
limits of sorting | Richard Cownie | 2009/08/22 07:27 PM |
limits of sorting | Richard Cownie | 2009/08/22 08:39 PM |
limits of sorting | ? | 2009/08/23 05:07 AM |
limits of sorting | Richard Cownie | 2009/08/23 05:53 AM |
limits of sorting | anonymous | 2009/08/23 11:42 AM |
useful link, thanks | Richard Cownie | 2009/08/23 05:23 PM |
limits of sorting | ? | 2009/09/04 04:05 AM |
limits of sorting | JasonB | 2009/08/23 09:26 AM |
wacky C++ features | Richard Cownie | 2009/08/24 07:13 AM |
wacky C++ features | a reader | 2009/08/24 09:59 PM |
wacky C++ features | Richard Cownie | 2009/08/25 03:18 AM |
wacky C++ features | a reader | 2009/08/25 07:04 AM |
wacky C++ features | Potatoswatter | 2009/08/25 10:21 PM |
wacky C++ features | none | 2009/08/26 05:47 AM |
wacky C++ features | Richard Cownie | 2009/08/26 08:09 AM |
wacky C++ features | Potatoswatter | 2009/08/27 06:25 AM |
wacky C++ features | Andi Kleen | 2009/08/25 12:06 AM |
wacky C++ features | Richard Cownie | 2009/08/25 03:10 AM |
wacky C++ features | Octoploid | 2009/08/25 03:40 AM |
wacky C++ features | Richard Cownie | 2009/08/25 05:15 AM |
wacky C++ features | Andi Kleen | 2009/08/25 07:58 AM |
thanks | Richard Cownie | 2009/08/25 08:07 AM |
thanks | Andi Kleen | 2009/08/25 11:28 AM |
wacky C++ features | anon | 2009/08/25 03:34 PM |
wacky C++ features | Andi Kleen | 2009/08/25 10:25 PM |
wacky C++ features | JasonB | 2009/08/25 01:13 AM |
wacky C++ features | Richard Cownie | 2009/08/25 02:32 AM |
exception | a reader | 2009/08/25 07:32 AM |
exception | Richard Cownie | 2009/08/25 07:57 AM |
exception | Potatoswatter | 2009/08/25 08:30 AM |
wacky C++ features | JasonB | 2009/08/25 08:56 PM |
correction | JasonB | 2009/08/25 09:47 PM |
correction | c++ | 2009/08/26 09:53 AM |
correction | JasonB | 2009/08/26 07:48 PM |
(new char[10]) does not have array type (NT) | Potatoswatter | 2009/08/27 06:27 AM |
correction | Potatoswatter | 2009/08/27 07:52 AM |
correction | c++ | 2009/08/27 09:29 AM |
comeau bugs and gcc features | Potatoswatter | 2009/08/27 09:51 AM |
comeau bugs and gcc features | Potatoswatter | 2009/08/27 11:28 AM |
wacky C++ features | Richard Cownie | 2009/08/26 09:17 AM |
wacky C++ features | JasonB | 2009/08/26 07:46 PM |
wacky C++ features | Richard Cownie | 2009/08/27 09:41 AM |
wacky C++ features | JasonB | 2009/08/27 09:33 PM |
wacky C++ features | Richard Cownie | 2009/08/28 01:24 AM |
wacky C++ features | Richard Cownie | 2009/08/28 01:27 AM |
wacky C++ features | Michael S | 2009/08/28 06:05 AM |
wacky C++ features | EduardoS | 2009/08/28 06:45 AM |
wacky C++ features | Richard Cownie | 2009/08/28 07:50 AM |
wacky C++ features | JasonB | 2009/08/28 04:56 PM |
wacky C++ features | JasonB | 2009/08/28 05:55 PM |
wacky C++ features | Richard Cownie | 2009/08/28 07:44 PM |
wacky C++ features | Konrad Schwarz | 2009/09/07 04:24 AM |
wacky C++ features | EduardoS | 2009/08/26 03:22 PM |
wacky C++ features | JasonB | 2009/08/26 06:47 PM |
wacky C++ features | Jukka Larja | 2009/08/27 12:03 AM |
wacky C++ features | JasonB | 2009/08/27 01:17 AM |
wacky C++ features | EduardoS | 2009/08/27 03:26 PM |
wacky C++ features | JasonB | 2009/08/27 06:31 PM |
wacky C++ features | EduardoS | 2009/08/28 03:25 PM |
wacky C++ features | JasonB | 2009/08/28 06:20 PM |
wacky C++ features | JasonB | 2009/08/27 09:56 PM |
Windows vs Unix/Linux culture | Richard Cownie | 2009/08/21 07:33 AM |
Windows vs Unix/Linux culture | Michael S | 2009/08/21 08:07 AM |
Windows vs Unix/Linux culture | Richard Cownie | 2009/08/21 08:33 AM |
Windows vs Unix/Linux culture | Paul | 2009/08/22 04:12 AM |
Windows vs Unix/Linux culture | anon | 2009/08/21 11:18 PM |
Windows vs Unix/Linux culture | Richard Cownie | 2009/08/21 11:45 PM |
Windows vs Unix/Linux culture | anon | 2009/08/22 12:48 AM |
Windows vs Unix/Linux culture | Paul | 2009/08/22 04:25 AM |
Windows vs Unix/Linux culture | Gian-Carlo Pascutto | 2009/08/22 07:02 AM |
Windows vs Unix/Linux culture | Paul | 2009/08/22 08:13 AM |
Windows vs Unix/Linux culture | rwessel | 2009/08/24 03:09 PM |
Windows vs Unix/Linux culture | JasonB | 2009/08/22 05:28 PM |
Windows vs Unix/Linux culture | Richard Cownie | 2009/08/22 06:22 PM |
Windows vs Unix/Linux culture | JasonB | 2009/08/22 06:52 PM |
Windows vs Unix/Linux culture | Richard Cownie | 2009/08/22 07:47 PM |
Encapsulation | Konrad Schwarz | 2009/09/03 04:49 AM |
Encapsulation | anon | 2009/09/03 10:05 AM |
Encapsulation | ? | 2009/09/03 11:38 AM |
Encapsulation | Andi Kleen | 2009/09/04 01:41 AM |
Encapsulation | anon | 2009/09/04 07:24 AM |
Encapsulation | Richard Cownie | 2009/09/04 07:34 AM |
Encapsulation | Konrad Schwarz | 2009/09/07 03:28 AM |
Encapsulation | Richard Cownie | 2009/09/07 04:04 PM |
Windows vs Unix/Linux culture | ? | 2009/09/03 11:51 AM |
Windows vs Unix/Linux culture | no thanks | 2009/08/23 10:36 AM |
Windows vs Unix/Linux culture | Richard Cownie | 2009/08/23 04:23 PM |
Windows vs Unix/Linux culture | JasonB | 2009/08/23 08:31 PM |
Windows vs Unix/Linux culture | Richard Cownie | 2009/08/24 12:10 AM |
Windows vs Unix/Linux culture | Jukka Larja | 2009/08/24 10:13 PM |
Windows vs Unix/Linux culture | JasonB | 2009/08/24 11:35 PM |
Windows vs Unix/Linux culture | Richard Cownie | 2009/08/25 03:04 AM |
Windows vs Unix/Linux culture | JasonB | 2009/08/25 11:48 PM |
Windows vs Unix/Linux culture | Richard Cownie | 2009/08/26 08:28 AM |
Windows vs Unix/Linux culture | JasonB | 2009/08/26 10:31 PM |
Windows vs Unix/Linux culture | Richard Cownie | 2009/08/26 08:43 AM |
Windows vs Unix/Linux culture | anon | 2009/08/26 01:48 PM |
Windows vs Unix/Linux culture | Richard Cownie | 2009/08/26 03:28 PM |
Windows vs Unix/Linux culture | JasonB | 2009/08/26 08:06 PM |
Windows vs Unix/Linux culture | Richard Cownie | 2009/08/27 03:44 AM |
Windows vs Unix/Linux culture | Rob Thorpe | 2009/08/27 05:51 AM |
Windows vs Unix/Linux culture | JasonB | 2009/08/23 09:07 PM |
Windows vs Unix/Linux culture | no thanks | 2009/08/23 09:44 PM |
Windows vs Unix/Linux culture | JasonB | 2009/08/24 12:34 AM |
Windows vs Unix/Linux culture | anon | 2009/08/23 09:46 PM |
limits of sorting | Richard Cownie | 2009/08/20 07:59 AM |
limits of sorting | Richard Cownie | 2009/08/20 09:27 AM |
limits of sorting | JasonB | 2009/08/20 08:55 PM |
limits of sorting | Richard Cownie | 2009/08/20 11:22 PM |
limits of sorting | JasonB | 2009/08/21 12:15 AM |
limits of sorting | Richard Cownie | 2009/08/21 04:47 AM |
limits of sorting | ? | 2009/08/20 11:42 PM |
limits of sorting | Richard Cownie | 2009/08/21 07:51 AM |
limits of sorting | Michael S | 2009/08/21 08:11 AM |
limits of sorting | Richard Cownie | 2009/08/21 08:38 AM |
limits of sorting | dmsc | 2009/08/20 07:56 PM |
limits of sorting | Richard Cownie | 2009/08/20 08:20 PM |
limits of sorting | Rob Thorpe | 2009/08/20 08:09 AM |
limits of sorting | Aaron Spink | 2009/08/20 12:19 AM |
limits of sorting | JasonB | 2009/08/20 01:55 AM |
limits of sorting | Michael S | 2009/08/18 07:12 AM |
limits of sorting | hobold | 2009/08/18 07:55 AM |
limits of sorting | rwessel | 2009/09/08 02:52 PM |
maximal theoretical sorting efficiency | Emil | 2009/09/08 07:06 PM |
maximal theoretical sorting efficiency | rwessel | 2009/09/08 10:04 PM |
maximal theoretical sorting efficiency | hobold | 2009/09/09 04:56 AM |
maximal theoretical sorting efficiency | Richard Cownie | 2009/09/09 09:10 AM |
maximal theoretical sorting efficiency | hobold | 2009/09/10 05:39 AM |
maximal theoretical sorting efficiency | Richard Cownie | 2009/09/10 08:05 AM |
maximal theoretical sorting efficiency | Potatoswatter | 2009/09/10 01:23 PM |
maximal theoretical sorting efficiency | dmsc | 2009/09/13 08:04 AM |
limits of sorting | Potatoswatter is back! | 2009/08/21 06:07 PM |
indeed it doesn't succeed in partitioning at all, but you get the idea ;) (NT) | Potatoswatter is back! | 2009/08/21 06:12 PM |
indeed it doesn't succeed in partitioning at all, but you get the idea ;) (NT) | Jouni Osmala | 2009/08/22 01:01 AM |
limits of sorting | hobold | 2009/08/22 07:25 AM |
limits of sorting | Potatoswatter | 2009/08/22 08:45 AM |
limits of sorting | David Kanter | 2009/08/22 10:16 AM |
limits of sorting | Jouni Osmala | 2009/08/22 12:01 PM |
Oops that was counting sort not bucket sort ;( | Jouni Osmala | 2009/08/22 12:07 PM |
close enough for my purposes | hobold | 2009/08/22 02:15 PM |
select vs. cmove | hobold | 2009/08/22 02:25 PM |
How much IPC | Gian-Carlo Pascutto | 2009/08/18 03:25 AM |
How much IPC | Vincent Diepeveen | 2009/08/19 06:46 AM |
How much IPC | _Arthur | 2009/08/19 09:32 AM |
How much IPC | hobold | 2009/08/18 04:17 AM |
How much IPC | Michael S | 2009/08/18 05:33 AM |
How much IPC | hobold | 2009/08/18 07:35 AM |
How much IPC | ? | 2009/08/18 12:20 PM |
How much IPC | _Arthur | 2009/08/18 12:33 PM |
Nit picking | David Kanter | 2009/08/18 02:17 PM |
Nit picking | _Arthur | 2009/08/18 02:37 PM |
Nit picking | Michael S | 2009/08/18 03:02 PM |
Nit picking | S. Rao | 2009/08/18 05:02 PM |
Nit picking | anon | 2009/08/19 03:03 AM |
Nit picking | Michael S | 2009/08/18 02:53 PM |
Nit picking | JasonB | 2009/08/18 07:16 PM |
How much IPC | ? | 2009/08/18 02:37 PM |
How much IPC | _Arthur | 2009/08/18 04:23 PM |
How much IPC | Matt Sayler | 2009/08/18 06:09 PM |
How much IPC | ? | 2009/08/18 11:59 PM |
nick's testcase | a reader | 2009/08/17 05:47 PM |
How much IPC | TruePath | 2009/09/27 10:00 AM |
Explicit dependency chains | David Kanter | 2009/09/30 07:56 PM |
How much IPC | TruePath | 2009/09/27 10:00 AM |
How much IPC | hobold | 2009/08/17 06:38 AM |
How much IPC | anon | 2009/08/16 09:59 PM |
Speeing Up Single Threads | TruePath | 2009/09/27 08:58 AM |
How much IPC | anon | 2009/08/15 08:01 PM |
How much IPC | EduardoS | 2009/08/16 07:06 AM |
How much IPC | sJ | 2009/08/16 09:48 PM |
Power7 vs. single threaded performance and licensing | anon | 2009/08/14 03:26 PM |
Power7 vs. single threaded performance and licensing | Linus Torvalds | 2009/08/14 04:04 PM |
Power7 vs. single threaded performance and licensing | Jonathan Kang | 2009/08/21 03:43 PM |
Power7 vs. single threaded performance and licensing | Linus Torvalds | 2009/08/21 04:08 PM |
Power7 vs. single threaded performance and licensing | Linus Torvalds | 2009/08/21 04:33 PM |
Power7 vs. single threaded performance and licensing | Jonathan Kang | 2009/08/22 08:57 AM |
Power7 vs. single threaded performance and licensing | Jukka Larja | 2009/08/22 11:04 PM |
Power7 vs. single threaded performance and licensing | Jonathan Kang | 2009/08/25 12:33 PM |
Power7 vs. single threaded performance and licensing | ? | 2009/08/22 12:51 AM |
Power7 vs. single threaded performance and licensing | anon | 2009/08/22 10:56 AM |
Power7 vs. single threaded performance and licensing | Linus Torvalds | 2009/08/22 11:38 AM |
Power7 vs. single threaded performance and licensing | ? | 2009/08/23 04:05 AM |
Power7 vs. single threaded performance and licensing | EduardoS | 2009/08/23 04:28 AM |
Programming Larrabee | ? | 2009/08/23 06:48 AM |
Programming Larrabee | EduardoS | 2009/08/23 07:41 AM |
Programming Larrabee | anon | 2009/08/23 08:29 AM |
Programming Larrabee | Potatoswatter | 2009/08/23 07:47 AM |
Programming Larrabee | Richard Cownie | 2009/08/23 09:11 AM |
Programming Larrabee | Potatoswatter | 2009/08/24 12:49 AM |
Programming Larrabee | ? | 2009/08/23 09:59 AM |
Programming Larrabee | Potatoswatter | 2009/08/24 12:44 AM |
Programming Larrabee | hobold | 2009/08/24 06:41 AM |
Programming Larrabee | none | 2009/08/24 08:15 AM |
Programming Larrabee | Richard Cownie | 2009/08/24 08:33 AM |
Programming Larrabee | Jukka Larja | 2009/08/24 10:30 PM |
Programming Larrabee | none | 2009/08/25 02:53 AM |
Programming Larrabee | mpx | 2009/08/25 09:16 AM |
Power7 vs. single threaded performance and licensing | Joe | 2009/08/24 09:38 AM |
Power7 vs. single threaded performance and licensing | Gabriele Svelto | 2009/08/14 04:35 AM |
Power7 vs. single threaded performance and licensing | anon | 2009/08/14 09:18 AM |
Power7 vs. single threaded performance and licensing | EduardoS | 2009/08/14 05:34 PM |
Power7 vs. single threaded performance and licensing | anon | 2009/08/15 07:30 AM |
Power7 vs. single threaded performance and licensing | anon | 2009/08/15 08:23 AM |
improving Netburst | AM | 2009/08/15 02:36 AM |
improving Netburst | anon | 2009/08/15 08:10 AM |
improving Netburst | Euronymous | 2009/08/15 09:35 AM |
improving Netburst | Michael S | 2009/08/15 02:18 PM |
Power7 vs. single threaded performance and licensing | Jonathan Kang | 2009/08/21 04:10 PM |
Power7 vs. single threaded performance and licensing | anon | 2009/08/22 10:46 AM |
Power7 vs. single threaded performance and licensing | Jonathan Kang | 2009/08/25 10:39 AM |
Power7 vs. single threaded performance and licensing | slacker | 2009/08/26 05:50 AM |
Power7 vs. single threaded performance and licensing | Jonathan Kang | 2009/08/26 09:12 AM |
Power7 vs. single threaded performance and licensing | Jonathan Kang | 2009/08/26 09:45 AM |
Power7 vs. single threaded performance and licensing | someone | 2009/08/26 11:29 AM |
Power7 vs. single threaded performance and licensing | David Kanter | 2009/08/26 11:47 AM |
Not necessarily | Daniel Bizó | 2009/08/14 03:53 AM |
new POWER7 info .. | Thu Nguyen | 2009/08/25 04:05 AM |
new POWER7 info .. | someone | 2009/08/25 06:47 AM |
new POWER7 info .. | hobold | 2009/08/25 07:50 AM |
new POWER7 info .. | G Webb | 2009/08/26 12:49 AM |
new POWER7 info .. | mpx | 2009/08/25 08:36 AM |
new POWER7 info .. | someone | 2009/08/25 09:16 AM |
new POWER7 info .. | Jesper Frimann | 2009/08/27 09:18 AM |
new POWER7 info .. | Linus Torvalds | 2009/08/27 11:53 AM |
new POWER7 info .. | someone | 2009/08/27 01:00 PM |
new POWER7 info .. | a reader | 2009/08/27 04:21 PM |
new POWER7 info .. | David Kanter | 2009/08/27 09:32 PM |
new POWER7 info .. | a reader | 2009/08/28 08:45 AM |
new POWER7 info .. | hobold | 2009/08/28 05:00 AM |
new POWER7 info .. | someone | 2009/08/28 06:51 AM |
new POWER7 info .. | hobold | 2009/08/28 07:44 AM |
new POWER7 info .. | someone | 2009/08/28 08:10 AM |
Non Autopar submissions for Nehalem | IlleglWpns | 2009/08/28 10:41 AM |
Non Autopar submissions for Nehalem | David Kanter | 2009/08/28 11:07 AM |
Non Autopar submissions for Nehalem | someone | 2009/08/28 12:00 PM |
new POWER7 info .. | mas | 2009/08/26 12:25 AM |
An EV8 lite? (NT) | anon | 2009/08/26 09:21 AM |
An EV8 lite? => Piranha? | M. | 2009/08/30 04:54 AM |
new POWER7 info .. | Mark Roulo | 2009/08/27 06:51 AM |
new POWER7 info .. | someone | 2009/08/27 07:03 AM |
new POWER7 info .. | a reader | 2009/08/27 09:55 AM |
new POWER7 info .. | someone | 2009/08/27 11:58 AM |
new POWER7 info .. | a reader | 2009/08/27 04:11 PM |
new POWER7 info .. | Gabriele Svelto | 2009/08/28 12:17 AM |
new POWER7 info .. | someone | 2009/08/28 05:27 AM |
new POWER7 info .. | a reader | 2009/08/28 09:07 AM |
OOOE for low power | David Kanter | 2009/08/28 11:15 AM |
OOOE for low power | someone | 2009/08/28 11:39 AM |
OOOE for low power | David Kanter | 2009/08/28 01:55 PM |
OOOE for low power | Mark Roulo | 2009/08/28 03:16 PM |
OOOE for low power | Mark Roulo | 2009/08/28 03:44 PM |
Atom uarch | David Kanter | 2009/08/28 08:19 PM |
OOOE for low power | David Kanter | 2009/08/28 08:07 PM |
OOOE for low power | someone | 2009/08/28 04:18 PM |
OOOE for low power | David Kanter | 2009/08/29 01:55 AM |
OOOE for low power | someone | 2009/08/29 07:21 AM |
OOOE for low power | a reader | 2009/08/29 09:14 AM |
OOOE for low power | someone | 2009/08/29 09:56 AM |
OOOE for low power | David Kanter | 2009/08/29 10:08 AM |
OOOE for low power | Michael S | 2009/08/29 11:27 AM |
OOOE for low power | a reader | 2009/08/29 04:50 PM |
OOOE for low power | anonymous | 2009/08/29 07:17 PM |
OOOE for low power | Michael S | 2009/08/30 12:07 AM |
OOOE for low power | Jonathan Kang | 2009/09/01 05:44 AM |
OOOE for low power | Michael S | 2009/09/01 04:21 PM |
OOOE for low power | Mark Roulo | 2009/09/01 05:53 PM |
OOOE for low power | Wilco | 2009/09/02 02:27 AM |
OOOE for low power | Mark Roulo | 2009/09/02 08:46 AM |
OOOE for low power | Wilco | 2009/09/02 04:52 PM |
Define "emulate" (NT) | Michael S | 2009/09/02 11:44 PM |
Define "emulate" | Wilco | 2009/09/03 12:33 AM |
Define "emulate" | none | 2009/09/03 04:46 AM |
Define "emulate" | Adrian | 2009/09/03 10:45 AM |
Define "emulate" | Wilco | 2009/09/03 02:20 PM |
Define "emulate" | none | 2009/09/03 10:41 PM |
Define "emulate" | Wilco | 2009/09/04 03:30 AM |
low power ARM chips | Michael S | 2009/10/31 02:32 PM |
low power ARM chips | Gabriele Svelto | 2009/10/31 04:05 PM |
low power ARM chips | Michael S | 2009/10/31 04:45 PM |
low power ARM chips | t | 2009/10/31 05:21 PM |
OOOE for low power | David Kanter | 2009/08/29 10:07 AM |
OOOE for low power | someone | 2009/08/29 12:40 PM |
OOOE for low power | a reader | 2009/08/29 05:03 PM |
OOOE for low power | anonymous | 2009/08/29 07:13 PM |
OOOE for low power | someone | 2009/08/30 07:35 AM |
OOOE for low power | David Kanter | 2009/08/30 02:32 PM |
OOOE for low power | Matt Sayler | 2009/08/31 01:38 PM |
OOOE for low power | David Kanter | 2009/08/30 12:07 PM |
OOOE for low power | Michael S | 2009/08/29 11:44 AM |
TTM | Michael S | 2009/08/29 12:24 PM |
TTM | Foo_ | 2009/08/29 01:40 PM |
TTM | Michael S | 2009/08/29 02:10 PM |
TTM | anon | 2009/08/29 07:33 PM |
TTM | Jukka Larja | 2009/08/29 09:49 PM |
TTM | anon | 2009/08/30 06:07 AM |
TTM | Jukka Larja | 2009/08/30 09:31 PM |
Area, power and Atom | David Kanter | 2009/08/30 10:36 PM |
Area, power and Atom | Michael S | 2009/08/31 12:18 AM |
Area, power and Atom | a reader | 2009/08/31 08:44 AM |
Area, power and Atom | Michael S | 2009/08/31 12:19 PM |
Area, power and Atom | a reader | 2009/08/31 02:53 PM |
Area, power and Atom | anonymous | 2009/08/31 04:17 PM |
Area, power and Atom | Gabriele Svelto | 2009/08/31 03:41 PM |
64-bit disabled Atoms | Foo_ | 2009/09/02 04:38 AM |
64-bit disabled Atoms | Robert David Graham | 2009/09/02 12:56 PM |
64-bit disabled Atoms | anon | 2009/09/02 02:14 PM |
64-bit disabled Atoms | anonymous | 2009/09/02 04:30 PM |
TTM | Michael S | 2009/08/30 11:49 PM |
TTM | Jukka Larja | 2009/08/31 11:23 PM |
TTM | Paul | 2009/08/30 06:38 AM |
TTM | Paul | 2009/08/30 06:40 AM |
TTM | Mark Roulo | 2009/08/30 09:50 AM |
TTM | Paul | 2009/08/30 09:54 AM |
TTM | Mark Roulo | 2009/08/30 10:16 AM |
TTM | Foo_ | 2009/09/02 04:31 AM |
OOOE for low power | Rob Thorpe | 2009/08/30 09:19 AM |
OOOE for low power | Michael S | 2009/08/29 11:16 AM |
OOOE for low power | Jukka Larja | 2009/08/29 09:40 PM |
OOOE for low power | Michael S | 2009/08/30 12:04 AM |
OOOE and cache/mem sizes | Richard Cownie | 2009/08/28 05:30 PM |
OOOE and cache/mem sizes | Linus Torvalds | 2009/08/31 10:53 PM |
OOOE and cache/mem sizes | Richard Cownie | 2009/09/01 04:15 AM |
OOOE and pipe length etc. | AM | 2009/09/01 08:35 AM |
OOOE and pipe length etc. | Jouni Osmala | 2009/09/01 08:57 AM |
OOOE and clock rate | AM | 2009/09/02 01:34 AM |
OOOE and clock rate | Jouni Osmala | 2009/09/02 05:35 AM |
OOOE and clock rate | Martin Høyer Kristiansen | 2009/09/02 06:19 AM |
OOOE and clock rate | anon | 2009/09/02 09:43 PM |
OOOE and clock rate | AM | 2009/09/03 02:52 AM |
OOOE and clock rate | Jouni Osmala | 2009/09/03 07:34 AM |
OOOE impacts | AM | 2009/09/04 02:04 AM |
OOOE impacts | David Kanter | 2009/09/04 10:12 AM |
OOOE impacts | Jouni Osmala | 2009/09/06 12:16 PM |
OOOE impacts | AM | 2009/09/07 03:47 AM |
OOOE impacts | Martin Høyer Kristiansen | 2009/09/07 06:03 AM |
Does IBM lie about PPC603 being OoO chip? | AM | 2009/09/08 03:13 AM |
No, but... | Michael S | 2009/09/08 07:05 AM |
No, but... | hobold | 2009/09/09 05:09 AM |
OOOE impacts | JS | 2009/09/07 06:34 AM |
Are Sandpile and others wrong about 0.28 um? | AM | 2009/09/08 03:12 AM |
OOOE impacts | someone | 2009/09/08 06:43 AM |
OOOE impacts | Jouni Osmala | 2009/09/07 07:48 AM |
OOOE costs | David Kanter | 2009/09/07 12:07 PM |
OOOE impacts | AM | 2009/09/08 03:11 AM |
OOOE impacts | Jouni Osmala | 2009/09/10 01:53 AM |
OOOE impacts | AM | 2009/09/11 04:35 AM |
OOOE impacts | Jouni Osmala | 2009/09/11 08:38 AM |
OOOE impacts | AM | 2009/09/12 05:06 AM |
OOOE impacts | Jouni Osmala | 2009/09/12 11:36 PM |
OOOE impacts | AM | 2009/09/14 04:39 AM |
OOOE impacts | Jouni Osmala | 2009/09/14 06:18 AM |
if-ex distance | AM | 2009/09/15 05:16 AM |
small addendum | AM | 2009/09/19 03:54 AM |
small addendum | Jouni Osmala | 2009/09/19 09:51 PM |
small addendum | AM | 2009/09/20 06:54 AM |
small addendum | Jouni Osmala | 2009/09/20 01:16 PM |
small addendum | Thiago Kurovski | 2009/09/20 04:51 PM |
small addendum | Jouni Osmala | 2009/09/20 09:21 PM |
small addendum | Thiago Kurovski | 2009/09/21 06:59 AM |
small addendum | AM | 2009/09/21 03:14 AM |
small addendum | Jukka Larja | 2009/09/21 10:21 PM |
small addendum | AM | 2009/09/22 03:01 AM |
small addendum | Jukka Larja | 2009/09/22 11:31 PM |
small addendum | AM | 2009/09/23 08:35 AM |
small addendum | Jukka Larja | 2009/09/23 10:31 PM |
small addendum | AM | 2009/09/24 12:13 AM |
OT metadiscussion | Jukka Larja | 2009/09/24 09:39 PM |
OT metadiscussion | AM | 2009/09/25 05:18 AM |
Back to bits | Michael S | 2009/09/25 07:14 AM |
Back to bits | Thiago Kurovski | 2009/09/25 11:24 AM |
Back to bits | Wilco | 2009/09/25 03:18 PM |
Back to bits | Thiago Kurovski | 2009/09/26 09:12 AM |
Back to bits | Michael S | 2009/09/26 08:54 AM |
Back to bits | Thiago Kurovski | 2009/09/26 09:05 AM |
Back to bits | Michael S | 2009/09/26 09:16 AM |
Agree, with very minor change. | Jouni Osmala | 2009/09/25 09:37 PM |
Back to bits | AM | 2009/09/26 06:16 AM |
Back to bits | Michael S | 2009/09/26 09:13 AM |
OT metadiscussion | David Kanter | 2009/09/25 12:23 PM |
OT metadiscussion | AM | 2009/09/26 05:55 AM |
OT metadiscussion | Jukka Larja | 2009/09/25 11:33 PM |
OT metadiscussion | AM | 2009/09/26 05:50 AM |
OT metadiscussion | Jukka Larja | 2009/09/27 02:16 AM |
OT metadiscussion | Michael S | 2009/09/27 04:58 AM |
OT metadiscussion | AM | 2009/09/28 04:07 AM |
OT metadiscussion | AM | 2009/09/28 03:43 AM |
OT metadiscussion | Jukka Larja | 2009/09/29 12:45 AM |
OT metadiscussion | AM | 2009/09/30 03:13 AM |
OT metadiscussion | Jukka Larja | 2009/10/01 01:34 AM |
OT metadiscussion | AM | 2009/10/01 04:05 AM |
OT metadiscussion | Jukka Larja | 2009/10/02 12:38 AM |
OT metadiscussion | AM | 2009/10/03 07:19 AM |
OT metadiscussion | Jukka Larja | 2009/10/04 03:38 AM |
OT metadiscussion | AM | 2009/10/04 08:27 AM |
OT metadiscussion | Jukka Larja | 2009/10/04 11:48 PM |
OT metadiscussion | AM | 2009/10/05 07:13 AM |
About teaching | Jukka Larja | 2009/10/05 11:36 PM |
About teaching | AM | 2009/10/06 04:37 AM |
About teaching | Jukka Larja | 2009/10/07 03:15 AM |
About teaching | anon | 2009/10/07 12:39 PM |
About teaching | AM | 2009/10/08 03:11 AM |
About teaching | Jukka Larja | 2009/10/09 04:10 AM |
About teaching | AM | 2009/10/09 05:40 AM |
About teaching | Jukka Larja | 2009/10/09 09:02 PM |
About teaching | AM | 2009/10/09 11:24 PM |
About teaching | Jukka Larja | 2009/10/10 10:50 PM |
About teaching | AM | 2009/10/12 02:02 AM |
About teaching | Jukka Larja | 2009/10/12 10:51 PM |
About teaching | AM | 2009/10/13 04:06 AM |
About teaching | Jukka Larja | 2009/10/13 11:33 PM |
About teaching | AM | 2009/10/14 03:36 AM |
About teaching | Jukka Larja | 2009/10/14 08:19 PM |
About teaching | AM | 2009/10/15 04:22 AM |
About teaching | Salvatore De Dominicis | 2009/10/12 02:23 AM |
About teaching | Dean Kent | 2009/10/12 12:25 PM |
About teaching | Salvatore De Dominicis | 2009/10/13 02:11 AM |
OT metadiscussion | Seni | 2009/09/26 06:26 AM |
OT metadiscussion | Wilco | 2009/09/26 08:08 AM |
OT metadiscussion | Jukka Larja | 2009/09/27 02:18 AM |
OT metadiscussion | Michael S | 2009/09/27 05:12 AM |
small addendum | Jouni Osmala | 2009/09/24 10:04 PM |
small addendum | AM | 2009/09/25 05:04 AM |
extra stage in EV6 | AM | 2009/09/26 06:29 AM |
PPC603 does OoOE | hobold | 2009/09/08 05:40 AM |
OOOE impacts | someone | 2009/09/08 05:39 AM |
EV6 | AM | 2009/09/09 04:33 AM |
OOOE and clock rate | Seni | 2009/09/02 09:11 AM |
OOOE and clock rate | Linus Torvalds | 2009/09/02 06:48 PM |
OOOE and clock rate | anon | 2009/09/02 11:55 PM |
OOOE and clock rate | Wilco | 2009/09/03 12:44 AM |
OOOE and clock rate | Jouni Osmala | 2009/09/03 01:02 AM |
OOOE and Itanium | AM | 2009/09/03 01:27 AM |
OOOE and clock rate | Martin Høyer Kristiansen | 2009/09/03 03:41 AM |
OOOE and clock rate | anon | 2009/09/03 01:12 AM |
OOOE and clock rate | Wilco | 2009/09/03 02:10 AM |
POWER6 skewed pipeline | Paul A. Clayton | 2009/09/03 11:22 AM |
POWER6 skewed pipeline | Anon4 | 2009/09/03 07:00 PM |
OOOE and clock rate | Mr. Camel | 2009/09/03 03:40 AM |
OOOE and clock rate | Richard Cownie | 2009/09/03 06:42 AM |
OOOE and pipe length etc. | Richard Cownie | 2009/09/01 09:01 AM |
OOOE and pipe length etc. | AM | 2009/09/02 01:32 AM |
OOOE and pipe length etc. | Richard Cownie | 2009/09/02 07:49 AM |
LRB choice of P54 | AM | 2009/09/03 01:40 AM |
LRB choice of P54 | Gian-Carlo Pascutto | 2009/09/03 01:45 AM |
LRB choice of P54 | AM | 2009/09/03 03:18 AM |
LRB choice of P54 | Gian-Carlo Pascutto | 2009/09/03 03:55 AM |
LRB choice of P54 | AM | 2009/09/03 04:28 AM |
LRB choice of P54 | Gian-Carlo Pascutto | 2009/09/03 05:29 AM |
Amount of cache per core matters,and mem bandwith too (NT) | Jouni Osmala | 2009/09/03 07:44 AM |
LRB choice of P54 | rwessel | 2009/09/03 02:31 PM |
LRB choice of P54 | AM | 2009/09/04 02:24 AM |
LRB choice of P54 | anon | 2009/09/03 06:40 AM |
LRB choice of P54 | a reader | 2009/09/03 09:20 AM |
LRB choice of P54 | anon | 2009/09/03 05:57 PM |
LRB choice of P54 | Jonathan Kang | 2009/09/03 02:30 PM |
LRB choice of P54 | David Kanter | 2009/09/03 04:38 PM |
LRB choice of P54 | Jonathan Kang | 2009/09/04 08:16 AM |
LRB choice of P54 | anon | 2009/09/03 06:07 PM |
LRB choice of P54 | AM | 2009/09/04 02:20 AM |
LRB choice of P54 | Jonathan Kang | 2009/09/04 08:13 AM |
LRB choice of P54 | Dan Downs | 2009/09/04 08:38 AM |
LRB choice of P54 | Dan Downs | 2009/09/05 04:36 AM |
LRB choice of P54 | Anon | 2009/09/05 02:44 PM |
LRB choice of P54 | AM | 2009/09/05 12:12 AM |
LRB choice of P54 | AM | 2009/09/04 02:18 AM |
LRB choice of P54 | anon | 2009/09/04 08:18 PM |
LRB choice of P54 | AM | 2009/09/04 11:53 PM |
LRB choice of P54 | anon | 2009/09/05 04:06 AM |
LRB choice of P54 | AM | 2009/09/05 09:14 AM |
LRB choice of P54 - Layout? | Anonymous | 2009/09/03 02:40 PM |
LRB choice of P54 - Layout? | anonymous | 2009/09/03 03:54 PM |
LRB choice of P54 | Jukka Larja | 2009/09/03 09:58 PM |
LRB choice of P54 | mpx | 2009/09/04 04:07 AM |
LRB choice of P54 | anon | 2009/09/03 02:02 AM |
OOOE and pipe length etc. | Gian-Carlo Pascutto | 2009/09/03 01:40 AM |
Larrabee: Pentium vs 486 vs 386 | Mark Roulo | 2009/09/03 04:26 PM |
Larrabee: Pentium vs 486 vs 386 | Michael S | 2009/09/03 05:14 PM |
Larrabee: Pentium vs 486 vs 386 | Mark Roulo | 2009/09/04 10:05 AM |
Larrabee: Pentium vs 486 vs 386 | Jonathan Kang | 2009/09/04 10:59 AM |
Larrabee: Pentium vs 486 vs 386 | Michael S | 2009/09/05 09:58 AM |
Larrabee: Pentium vs 486 vs 386 | James | 2009/09/07 03:15 AM |
Larrabee: Pentium vs 486 vs 386 | Mark Roulo | 2009/09/07 07:44 PM |
OOOE and pipe length etc. | Michael S | 2009/09/03 05:42 PM |
LRB core | AM | 2009/09/04 02:09 AM |
LRB core | Michael S | 2009/09/04 05:07 AM |
LRB core | anon | 2009/09/04 08:27 PM |
LRB core | Michael S | 2009/09/05 10:12 AM |
LRB core | anon | 2009/09/05 11:03 PM |
reasons for split I/D L1 caches | Michael S | 2009/09/06 04:10 AM |
reasons for split I/D L1 caches | anon | 2009/09/06 06:32 AM |
reasons for split I/D L1 caches | ? | 2009/09/06 10:35 AM |
reasons for split I/D L1 caches | megol | 2009/09/06 03:39 PM |
reasons for split I/D L1 caches | ? | 2009/09/07 04:20 AM |
reasons for split I/D L1 caches | anon | 2009/09/07 06:25 AM |
cache hinting | ? | 2009/09/07 07:10 AM |
cache hinting | anon | 2009/09/07 07:35 AM |
cache hinting | ? | 2009/09/07 09:10 AM |
cache hinting | anon | 2009/09/07 09:49 AM |
cache hinting | ? | 2009/09/07 10:37 AM |
Split and unified caches | David Kanter | 2009/09/06 01:38 PM |
Split and unified caches | anon | 2009/09/06 11:15 PM |
Split and unified caches | Michael S | 2009/09/07 12:40 AM |
Split and unified caches | anon | 2009/09/07 02:24 AM |
Split and unified caches | David Kanter | 2009/09/07 12:51 AM |
Split and unified caches | anon | 2009/09/07 02:13 AM |
LRB core | AM | 2009/09/05 12:08 AM |
LRB core | Linus Torvalds | 2009/09/05 10:47 AM |
LRB core | David Kanter | 2009/09/04 01:23 PM |
LRB core | Anon | 2009/09/04 06:32 PM |
LRB core | David Kanter | 2009/09/04 10:15 PM |
LRB core | Michael S | 2009/09/05 10:21 AM |
OOOE and cache/mem sizes | a reader | 2009/09/01 09:19 AM |
OOOE and cache/mem sizes | Richard Cownie | 2009/09/01 09:43 AM |
snapdraon? | Michael S | 2009/08/28 06:10 AM |
snapdraon? | a reader | 2009/08/28 08:51 AM |
Thanks (NT) | Michael S | 2009/08/29 12:53 PM |
snapdraon? | Paul | 2009/08/28 01:12 PM |
new POWER7 info .. | EduardoS | 2009/08/27 03:41 PM |
new POWER7 info .. | Jesper Frimann | 2009/08/28 05:03 AM |
Single threaded performance | David Kanter | 2009/08/28 10:52 AM |
Hot Chips XXI Preview online | hobold | 2009/08/13 07:30 AM |