{"push_id":2624471481,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"29b62b2f9eb0a8044ad7119970acd31b29147ffa","before":"9ff5a43cf48ac134ead491b52a3da01ffb6f31b5","commits":[{"sha":"29b62b2f9eb0a8044ad7119970acd31b29147ffa","author":{"name":"Sameeh Jubran","email":"0a911daba6e3bf1ebda689ee3bdc069f3d45a844@daynix.com"},"message":"NetKVM: TX: Drop heavy DPC scheduling\n\nIn commit e8f319fdc09837dc27fce1b8abb3496593e9dc10 the lock free queue was\nintroduced as an alternative implementation to the previous one which\nrequired acquiring the TX's path lock for NBLs sent by Windows. The\nintention for the implementation introduced was that this lock acquirement\nwould be dropped in favour of scheduling a DPC upon sending an NBL instead.\n\nWhile this DPC scheduling approach works it does introduce a heavy DPC\nscheduling on the environment, the overhead can be as high as executing a\nDPC for each NBL sent by Windows in the worst case scenario. In general\nWindows should drop duplicate DPCs but it seems that it is not doing so\nefficiently or else it is executing a DPC upon each schedule request by us\nin a heavy load environment.\n\nAn alternative implementation which would probably allow us to keep the\nDPC scheduling implementation is adding a mechanism to identify bursts and\nforecast when we are receiving a high packet rate and adapt (lower) the\nDPC scheduling accordingly.\n\nThis commit enables the HCK/HLK 1c_Mini6PerfSend test to pass as it was\nstuck due to this heavy DPC load environment.\n\nSigned-off-by: Sameeh Jubran <sameeh@daynix.com>","distinct":true,"url":"https://api.github.com/repos/virtio-win/kvm-guest-drivers-windows/commits/29b62b2f9eb0a8044ad7119970acd31b29147ffa"}]}
{"actor":{"display_login":"YanVugenfirer"}}