[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [microblaze-uclinux] MicroBlaze MMU support test release now available

Those numbers seem extremely low. I can get 8-9Mbps tx through the xilinx emac on the 1600E reference board with petalinux .20 without even trying. That was at 66Mhz. Have you run the numbers on the non-mmu petalinux versions? 
Or are you a BlueCat salesman ;-)

Bob Cutler wrote:

John Williams wrote:

Hi
I wrote:
I'm pleased to announce that we have a test release available for MicroBlaze MMU support in the PetaLinux 2.6.20 kernel.
Well it's 7 days and > 150 downloads later - any reports so far about the kernel itself? Anyone managed to crash it?
I'm aware of minor tool/build gremlins and they'll be sorted, plus we also need to reimplement the old-style kernel+romfs image.bin (instead of the rootfs.cpio stuff). These will happen soon. 

THanks,

John


Hi John,

I did some further network testing of petalinux-mmu-v0.10.  I used the
nuttcp network testing tool to test unidirectional TCP and UDP traffic.
For all tests, I ran the server on the MicroBlaze with the "nuttcp -S"
command.  For the tests over Ethernet, I ran the client on a PC with
a 100BASE-T NIC connected directly to the MicroBlaze board with a
crossover cable.  For the loopback device test, I ran the client on
the MicroBlaze.  I used the Xilinx Spartan-3A DSP S3D1800A board
running Xilinx's MicroBlaze reference design for this board with the
CPU clock at 62.5 MHz.  Here are the tests I ran using the same FPGA
bitstream for two OS's:

Test                        petalinux-mmu-v0.10   BlueCat 2.4.2   Ratio
-------------------------   -------------------   -------------   -----
TCP/IP : PC <- microblaze    2.7664 Mbps           7.7408 Mbps    2.798
TCP/IP : PC -> microblaze    2.0058 Mbps           3.7754 Mbps    1.882
UDP/IP : PC <- microblaze    2.2402 Mbps           3.9464 Mbps    1.762
UDP/IP : PC -> microblaze    0.0000 Mbps           4.9938 Mbps    -----
TCP/IP : loopback device    11.1282 Mbps          15.3766 Mbps    1.382
UDP/IP : loopback device     4.2587 Mbps          11.6176 Mbps    2.728

The client commands I used on the PC for the first four tests are:

Test                        Command
-------------------------   -------------------------------------
TCP/IP : PC <- microblaze   nuttcp -r -T60 10.25.1.201
TCP/IP : PC -> microblaze   nuttcp -t -T60 10.25.1.201
UDP/IP : PC <- microblaze   nuttcp -r -u -T60 -Ri100m 10.25.1.201
UDP/IP : PC -> microblaze   nuttcp -t -u -T60 -Ri5000 10.25.1.201

The client commands I used on the MicroBlaze for the last two tests are:

Test                        Command
-------------------------   ---------------------------------
TCP/IP : loopback device    nuttcp -T60 127.0.0.1
UDP/IP : loopback device    nuttcp -u -T60 -Ri1000m 127.0.0.1

There is no transfer time for "UDP/IP : PC -> microblaze" on PetaLinux
since I can not get it to receive UDP traffic no matter what nuttcp
options I try to rate limit, etc.  With some options, I can get it to
hang PetaLinux such that neither the serial console or ping from the
PC work until a reboot of PetaLinux.  Once I got PetaLinux to panic by
doing "ifconfig -a" repeatedly while the UDP test was running.  In both
cases, I was using the "nuttcp -t -u -T60 -Ri50m 10.25.1.201" client
command on the PC.  Here is the output from the panic:

~ # ifconfig -a
 Registers dump: mode=1
 Registers dump: mode=1
 r1=C0009778, r2=00000000, r3=30E0EA61, r4=0B6E0000
 r5=C00ED96C, r6=00010000, r7=00000001, r8=00000000
 r9=00000001, r10=C19AC000, r11=00000000, r12=C0006F14
 r13=00000000, r14=00000000, r15=C001916C, r16=00000001
 r17=00000000, r18=FFFFFFFF, r19=00989680, r20=00000000
 r21=00000000, r22=00000000, r23=00000000, r24=00000000
 r25=00000000, r26=00000000, r27=00000000, r28=00000000
 r29=00000000, r30=00000000, r31=C00ED96C, rPC=C0009778
 ear=C00EDA74, esr=00000470
Oops: kernel access of bad area, sig: 11
 Registers dump: mode=1
 r1=C0009778, r2=00000000, r3=30E0EA61, r4=0B6E0000
 r5=C00ED96C, r6=00010000, r7=00000001, r8=00000000
 r9=00000001, r10=C19AC000, r11=00000000, r12=C0006F14
 r13=00000000, r14=00000000, r15=C001916C, r16=00000001
 r17=00000000, r18=FFFFFFFF, r19=00989680, r20=00000000
 r21=00000000, r22=00000000, r23=00000000, r24=00000000
 r25=00000000, r26=00000000, r27=00000000, r28=00000000
 r29=00000000, r30=00000000, r31=C00ED96C, rPC=C0009778
 ear=C00EDA74, esr=00000470
Kernel panic - not syncing: Aiee, killing interrupt handler!
<0>Rebooting in 120 seconds..

Let me know if you have any questions or suggestions for fixes.

Thanks,
Bob

___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/ 



___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/