On 6/26/23 19:46, David Marchand wrote:
> On Mon, Jun 26, 2023 at 4:05 PM David Marchand
> wrote:
>>
>> On Mon, Jun 26, 2023 at 3:19 PM Ilya Maximets wrote:
- if the UFO feature is "restored" in the master branch, OVS can't
expose CSUM if the guest negotiated UFO.
>>>
>>> Yep. IIUC,
On Mon, Jun 26, 2023 at 4:05 PM David Marchand
wrote:
>
> On Mon, Jun 26, 2023 at 3:19 PM Ilya Maximets wrote:
> > > - if the UFO feature is "restored" in the master branch, OVS can't
> > > expose CSUM if the guest negotiated UFO.
> >
> > Yep. IIUC, that will require un-doing/re-wrking some of
On 6/26/23 16:05, David Marchand wrote:
> On Mon, Jun 26, 2023 at 3:19 PM Ilya Maximets wrote:
>>> - if the UFO feature is "restored" in the master branch, OVS can't
>>> expose CSUM if the guest negotiated UFO.
>>
>> Yep. IIUC, that will require un-doing/re-wrking some of the changes Mike
>> did
On Mon, Jun 26, 2023 at 3:19 PM Ilya Maximets wrote:
> > - if the UFO feature is "restored" in the master branch, OVS can't
> > expose CSUM if the guest negotiated UFO.
>
> Yep. IIUC, that will require un-doing/re-wrking some of the changes Mike
> did in order to restore ability to disable
On 6/26/23 11:37, David Marchand wrote:
> On Fri, Jun 23, 2023 at 11:52 PM Ilya Maximets wrote:
But we can't really do that from the OVS side, can we?
DPDK will clear the bit even if we enable it...
>>>
>>> Hum, I did not test it yet, but I was thinking of calling
>>>
On Mon, Jun 26, 2023 at 11:37 AM David Marchand
wrote:
> > Currently possible configurations:
> >
> > 1. CSUM + TSO + ___ + ___ OVS 3.1 with userspace-tso=true
> > 2. + TSO + ECN + ___ OVS 3.1 with userspace-tso=false
> > 3. + ___ + ECN + UFO OVS 2.11
> >
[snip]
> I don't
On Fri, Jun 23, 2023 at 11:52 PM Ilya Maximets wrote:
> >> But we can't really do that from the OVS side, can we?
> >> DPDK will clear the bit even if we enable it...
> >
> > Hum, I did not test it yet, but I was thinking of calling
> > rte_vhost_driver_enable_features.
> > Now that I look at the
On 6/23/23 23:52, Ilya Maximets wrote:
On 6/23/23 19:33, David Marchand wrote:
On Fri, Jun 23, 2023 at 5:14 PM Ilya Maximets wrote:
On 6/23/23 15:16, David Marchand wrote:
On Wed, Jun 21, 2023 at 12:13 AM Ilya Maximets wrote:
On 6/14/23 21:03, Mike Pattrick wrote:
The netdev receiving
On 6/23/23 19:33, David Marchand wrote:
> On Fri, Jun 23, 2023 at 5:14 PM Ilya Maximets wrote:
>> On 6/23/23 15:16, David Marchand wrote:
>>> On Wed, Jun 21, 2023 at 12:13 AM Ilya Maximets wrote:
On 6/14/23 21:03, Mike Pattrick wrote:
> The netdev receiving packets is supposed to
On Fri, Jun 23, 2023 at 5:14 PM Ilya Maximets wrote:
> On 6/23/23 15:16, David Marchand wrote:
> > On Wed, Jun 21, 2023 at 12:13 AM Ilya Maximets wrote:
> >>
> >> On 6/14/23 21:03, Mike Pattrick wrote:
> >>> The netdev receiving packets is supposed to provide the flags
> >>> indicating if the L4
On 6/23/23 15:16, David Marchand wrote:
> On Wed, Jun 21, 2023 at 12:13 AM Ilya Maximets wrote:
>>
>> On 6/14/23 21:03, Mike Pattrick wrote:
>>> The netdev receiving packets is supposed to provide the flags
>>> indicating if the L4 checksum was verified and it is OK or BAD,
>>> otherwise the
On Wed, Jun 21, 2023 at 12:13 AM Ilya Maximets wrote:
>
> On 6/14/23 21:03, Mike Pattrick wrote:
> > The netdev receiving packets is supposed to provide the flags
> > indicating if the L4 checksum was verified and it is OK or BAD,
> > otherwise the stack will check when appropriate by software.
>
On 6/21/23 00:14, Ilya Maximets wrote:
> On 6/14/23 21:03, Mike Pattrick wrote:
>> The netdev receiving packets is supposed to provide the flags
>> indicating if the L4 checksum was verified and it is OK or BAD,
>> otherwise the stack will check when appropriate by software.
>>
>> If the packet
On 6/14/23 21:03, Mike Pattrick wrote:
> The netdev receiving packets is supposed to provide the flags
> indicating if the L4 checksum was verified and it is OK or BAD,
> otherwise the stack will check when appropriate by software.
>
> If the packet comes with good checksum, then postpone the
>
The netdev receiving packets is supposed to provide the flags
indicating if the L4 checksum was verified and it is OK or BAD,
otherwise the stack will check when appropriate by software.
If the packet comes with good checksum, then postpone the
checksum calculation to the egress device if needed.
15 matches
Mail list logo
