Thanks again.
I meant that when I stop transmit, the IX bus device status shows no
packet
been received .
I didn't stop it after "n" packets are received, so if you say that the
transmitted packets are not cycled back as the recieve packets, what could
be the reason to this situation?
----- Original Message -----
From: "Abhijeet Joglekar"
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