> I looked into this, and discovered that the gcc 2.96 compiler turned my > rep movsd code into a rep movsb (???) with some evil looking C++ style If its hand coded asm then gcc shouldnt have touched it. If its an implicit memcpy then gcc will generate inline code designed for main memory copying. Do you have a small example chunk of code showing this ? > They deviated by 30%, indicating that my MTRR write combining optimization > was not working properly in sci copy mode. That would explain the %age certainly. How it happened is the next question - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- Re: [OT] Re: PCI-SCI Drivers v1.1-7 r... Tim Wright
- Re: [OT] Re: PCI-SCI Drivers v1.1... Jeff V. Merkey
- Re: [OT] Re: PCI-SCI Drivers v1.1... Alan Cox
- Re: [OT] Re: PCI-SCI Drivers v1.1... Jeff V. Merkey
- PCI-SCI Build Problems on RedHat ... Jeff V. Merkey
- Re: PCI-SCI Build Problems on Red... Larry
- Re: PCI-SCI Drivers v1.1-7 released David Howells
- Re: PCI-SCI Drivers v1.1-7 released Jeff V. Merkey
- Re: PCI-SCI Drivers v1.1-7 released Alan Cox
- Re: PCI-SCI Drivers v1.1-7 released Jeff V. Merkey
- Re: PCI-SCI Drivers v1.1-7 released Alan Cox
- Re: PCI-SCI Drivers v1.1-7 released Jeff V. Merkey
- Re: PCI-SCI Drivers v1.1-7 released Alan Cox
- Re: PCI-SCI Drivers v1.1-7 released Alan Cox
- Re: PCI-SCI Drivers v1.1-7 released Jeff V. Merkey
- Re: PCI-SCI Drivers v1.1-7 released Alan Cox
- Re: PCI-SCI Drivers v1.1-7 released Jeff V. Merkey