On 3/7/24 14:22, Kevin Traynor wrote:
> On 05/03/2024 17:31, Ilya Maximets wrote:
>> On 3/5/24 18:13, Kevin Traynor wrote:
>>> On 05/03/2024 15:22, Ilya Maximets wrote:
It's hard to debug situations where driver rejects packets for some
reason. Dumping out the mbuf should help with debug
On 05/03/2024 17:31, Ilya Maximets wrote:
> On 3/5/24 18:13, Kevin Traynor wrote:
>> On 05/03/2024 15:22, Ilya Maximets wrote:
>>> It's hard to debug situations where driver rejects packets for some
>>> reason. Dumping out the mbuf should help with debugging.
>>>
>>> Sample output looks like this:
On 3/5/24 18:13, Kevin Traynor wrote:
> On 05/03/2024 15:22, Ilya Maximets wrote:
>> It's hard to debug situations where driver rejects packets for some
>> reason. Dumping out the mbuf should help with debugging.
>>
>> Sample output looks like this:
>>
>> |netdev_dpdk(pmd-c03/id:8)|DBG|ovs-p1: I
On 05/03/2024 15:22, Ilya Maximets wrote:
> It's hard to debug situations where driver rejects packets for some
> reason. Dumping out the mbuf should help with debugging.
>
> Sample output looks like this:
>
> |netdev_dpdk(pmd-c03/id:8)|DBG|ovs-p1: Invalid packet:
> dump mbuf at 0x1180bce140
It's hard to debug situations where driver rejects packets for some
reason. Dumping out the mbuf should help with debugging.
Sample output looks like this:
|netdev_dpdk(pmd-c03/id:8)|DBG|ovs-p1: Invalid packet:
dump mbuf at 0x1180bce140, iova=0x2cb7ce400, buf_len=2176
pkt_len=64, ol_flag
