Quantcast
Viewing all articles
Browse latest Browse all 4405

process 4 receive packets only after 4 tx packets processing happened

Hi Sandy

I'm so sorry I didn't describe clearly and didn't give you the Ping details early.

The VF (iPXE) can ping the PF(Linux) successfully since the second tips.

animy 撰写:

 

Hi,Sandy

Thanks for your reply.

The driver i used is based on Linux-kernel 3.17.6 andthis problem have been solved by ignoring the protocol differences in transmit.

And there is a new problem occurred that shows as follows:

1. after transmit be called 4 times that process 4 transmit  packets. (solved. we have fixed it to one transmit,one process tx packet).

2. process 4 receive packets only after 4 tx packets processing happened. (not solved)

i don't known where or what register makes the 4 receive packets be processed together after processing 4 tx packets.

Could you give me a help?

 

Regards!

Animy

the problem iPXE logs show that only after four packets received, the DD bit in the receive descriptor WB format will be set.

and logs show as following format:

transmit

transmit

transmit

transmit

receive

receive

receive

receive

ping success!

and the response time as follows:

64 bytes from 192.168.57.81: icmp_seq=4 ttl=64 time=3039 ms

64 bytes from 192.168.57.81: icmp_seq=5 ttl=64 time=2034 ms

64 bytes from 192.168.57.81: icmp_seq=6 ttl=64 time=1032 ms

64 bytes from 192.168.57.81: icmp_seq=7 ttl=64 time=35.0 ms

When I use VF(linux) ping PF(Linux),the average response time only be 0.03ms

 

If you have any other confusion about this issue description, please contact me. And I look forward to your ideas about this issue.

 

Sincerely,

Animy


Viewing all articles
Browse latest Browse all 4405

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>