• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 212 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TM4C1294NCPDT: TM4C1294NCPDT - ETHERNET MAXIMUM PACKET TRANSFER

Aravind sr
Intellectual 300 points
Part Number: TM4C1294NCPDT

Hi Team,

We are working on ethernet data transfer. We are looking to achieve maximum packet can be send in a second . For example if the packet data size was 1514B . We can acheive 7817 packets per seconds  and for 64B data the packets can be 10117 packets was acheived. 

But we need to transfer 68052 packets per second for data length 64B .Is it possible?

Thanks and Regards,

Aravind S.R

  • 0
    TI__Guru**** 191886 points
    Aravind sr said:
    For example if the packet data size was 1514B . We can acheive 7817 packets per seconds  and for 64B data the packets can be 10117 packets was acheived. 

    Hi,

      Is 10117 packets your empirical data, or in another word, 10117 is what you measure when your packet size is 64B. Please note that a small packet size will have a much greater overhead percentage.  A smallest Ethernet frame is normally 64B. If your payload size is only 64B then your overhead is almost 50%. The overhead will include the Ethernet header, IP header and TCP header all encapsulated into the Ethernet frame on top your payload. There is a also the software side of overhead. Each time you try to transmit a small packet, you will need to go through the TCP/IP stack, not just sending the data out but also all the TCP handshakes (SYC, ACK and etc) between the transmitter and the receiver.  I think all of these will contribute to a less efficient throughput.