Thanks for your reply.
I'll try to explain my second question.
When I ran the simulator, I've noticed that in case that the transmit
doesn't works ( I stop to send packets from some reason) the receive also
stops.
I assume that in the beginning of the simulation the receiving packets are
created by the script command, and then the transmitted packets go back as
a
received packets.
My question is: if there is some way that the received packets won't be
the
transmitted packets,
so in case I stop transmitting, the receiving continue.
I hope that now the question is more clear. Thanks!
----- Original Message -----
From: "Abhijeet Joglekar"
I'm working of L3fwd16_RFC1812. I would like to check my program with packets in different sizes (random if possible)
Is any of you can explain me how can I do that? or maybe you have more complicate packet generator that you can send me?
If you are running your application on the simulator, then the Workbench allows you to create a packet stream with different frame sizes and
choose
a random option. Check out the IXP1200 Developer Tool Users Guide in the Intel documentation.
Another question - How do I change the dependency of the receive and transmit in the project ? (I want the the receive microengines will send packets all the time, without depend in the transmit rate)
Can you rephrase this question? I am not sure I understood it.
-- abhijeet
I'll try to explain my second question. When I ran the simulator, I've noticed that in case that the transmit doesn't works ( I stop to send packets from some reason) the receive also stops.
What do you mean by "receive stops"? Does the simulator give an error and stop, or the IX bus device status shows no packet been received ? Packets should be received at the port continously, unless you have specifically selected that packet reception should be stopped after some "n" packets are received. Ofcourse, the ingress microcode might drop those packets, if there arent enough buffers or if transmit is not releasing buffers.
I assume that in the beginning of the simulation the receiving packets are created by the script command, and then the transmitted packets go back as ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ a received packets.
> My question is: if there is some way that the received packets won't be
> the
> transmitted packets,
> so in case I stop transmitting, the receiving continue.
The transmitted packets are not cycled back as the recieve packets, if
that is what you are asking.
For instance, you can turn off Egress completely, and in ingress code,
simply count packets and then drop them and release the buffer handle
Packet reception should still work.
-- abhijeet
participants (2)
-
Abhijeet Joglekar -
Bracha Hod