* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-atomic passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/o3-timing passed.
* build/ALPHA_SE/tests/fast/quick/50.memtest/alpha/linux/memtest passed.
*
What's still left to do for stable? There's the SMT regression
failure. Korey or Kevin can you guys look into that so we can get
this done? Is there anything else? I have stuff just waiting to get
into the tree and I'm holding off for this stable release.
Nate
I agree with Ali, any message under a cache line in length should be
just fine. In fact, in some networks all messages might have to be a
cache line in length.
Nate
On Fri, Sep 5, 2008 at 9:07 AM, Ali Saidi [EMAIL PROTECTED] wrote:
I don't think there should be any problem with these
I have two major comments. First, you can use a DmaPort so you can
transmit an receive. Second, whatever ends up happening with
interrupts, I'd like us to look fixing up all of the interrupt
mechanism for all ISAs while we're at it. It's already pretty
disgusting. I'd like to see all ISAs send
Statistics cleanup? gcc 4.2?
Ali
On Sep 6, 2008, at 1:25 PM, nathan binkert wrote:
What's still left to do for stable? There's the SMT regression
failure. Korey or Kevin can you guys look into that so we can get
this done? Is there anything else? I have stuff just waiting to get
into
On Sep 6, 2008, at 4:26 PM, Gabe Black wrote:
There are two major problems with using the DmaPort. First, I'd want
to
send the interrupt -now- not when the DMA queuing latency, etc gets
used
up. Second, DmaPort will fragment a packet which, while maybe
necessary
in some cases, will
There are two major problems with using the DmaPort. First, I'd want to
send the interrupt -now- not when the DMA queuing latency, etc gets used
up. Second, DmaPort will fragment a packet which, while maybe necessary
in some cases, will break the atomicity requirements for the interrupt