search for: checksum_complete

..., and according to the comment > > > > > in skbuff.h > > > > > > > > > > > > > > > " > > > > > * The hardware you're dealing with doesn't calculate the full checksum > > > > > * (as in CHECKSUM_COMPLETE), but it does parse headers and verify > > > > > checksums > > > > > * for specific protocols. For such packets it will set > > > > > CHECKSUM_UNNECESSARY > > > > > * if their checksums are okay. skb->csum is still undefined i...

..., and according to the comment > > > > > in skbuff.h > > > > > > > > > > > > > > > " > > > > > * The hardware you're dealing with doesn't calculate the full checksum > > > > > * (as in CHECKSUM_COMPLETE), but it does parse headers and verify > > > > > checksums > > > > > * for specific protocols. For such packets it will set > > > > > CHECKSUM_UNNECESSARY > > > > > * if their checksums are okay. skb->csum is still undefined i...

...; encapsulations. This yeilds a significant perfromance improvement >> (still testing remote checksum code). >> >> An addition extension that is unfinished (due to still testing for any >> side-effects) is checksum passthrough to support drivers that set >> CHECKSUM_COMPLETE. This would eliminate the need for guests to compute >> the software checksum. >> >> This series only takes care of virtio net. I have addition patches for the >> host side (vhost and tap/macvtap as well as qemu), but wanted to get feedback >> on the general approach...

...; encapsulations. This yeilds a significant perfromance improvement >> (still testing remote checksum code). >> >> An addition extension that is unfinished (due to still testing for any >> side-effects) is checksum passthrough to support drivers that set >> CHECKSUM_COMPLETE. This would eliminate the need for guests to compute >> the software checksum. >> >> This series only takes care of virtio net. I have addition patches for the >> host side (vhost and tap/macvtap as well as qemu), but wanted to get feedback >> on the general approach...

..., and according to the comment >>>>>> in skbuff.h >>>>>> >>>>>> >>>>>> " >>>>>> * The hardware you're dealing with doesn't calculate the full checksum >>>>>> * (as in CHECKSUM_COMPLETE), but it does parse headers and verify >>>>>> checksums >>>>>> * for specific protocols. For such packets it will set >>>>>> CHECKSUM_UNNECESSARY >>>>>> * if their checksums are okay. skb->csum is still undefined...

...d possible other > encapsulations. This yeilds a significant perfromance improvement > (still testing remote checksum code). > > An addition extension that is unfinished (due to still testing for any > side-effects) is checksum passthrough to support drivers that set > CHECKSUM_COMPLETE. This would eliminate the need for guests to compute > the software checksum. > > This series only takes care of virtio net. I have addition patches for the > host side (vhost and tap/macvtap as well as qemu), but wanted to get feedback > on the general approach first. > > Vl...

...s. This yeilds a significant perfromance improvement >>> (still testing remote checksum code). >>> >>> An addition extension that is unfinished (due to still testing for any >>> side-effects) is checksum passthrough to support drivers that set >>> CHECKSUM_COMPLETE. This would eliminate the need for guests to compute >>> the software checksum. >>> >>> This series only takes care of virtio net. I have addition patches for the >>> host side (vhost and tap/macvtap as well as qemu), but wanted to get feedback >>> on...

...gnificant perfromance improvement >>>> (still testing remote checksum code). >>>> >>>> An addition extension that is unfinished (due to still testing for any >>>> side-effects) is checksum passthrough to support drivers that set >>>> CHECKSUM_COMPLETE. This would eliminate the need for guests to compute >>>> the software checksum. >>>> >>>> This series only takes care of virtio net. I have addition patches for the >>>> host side (vhost and tap/macvtap as well as qemu), but wanted to get feedback...

...gnificant perfromance improvement >>>> (still testing remote checksum code). >>>> >>>> An addition extension that is unfinished (due to still testing for any >>>> side-effects) is checksum passthrough to support drivers that set >>>> CHECKSUM_COMPLETE. This would eliminate the need for guests to compute >>>> the software checksum. >>>> >>>> This series only takes care of virtio net. I have addition patches for the >>>> host side (vhost and tap/macvtap as well as qemu), but wanted to get feedback...

...support GSO with udp tunnel and possible other encapsulations. This yeilds a significant perfromance improvement (still testing remote checksum code). An addition extension that is unfinished (due to still testing for any side-effects) is checksum passthrough to support drivers that set CHECKSUM_COMPLETE. This would eliminate the need for guests to compute the software checksum. This series only takes care of virtio net. I have addition patches for the host side (vhost and tap/macvtap as well as qemu), but wanted to get feedback on the general approach first. Vladislav Yasevich (6): virtio-ne...

...support GSO with udp tunnel and possible other encapsulations. This yeilds a significant perfromance improvement (still testing remote checksum code). An addition extension that is unfinished (due to still testing for any side-effects) is checksum passthrough to support drivers that set CHECKSUM_COMPLETE. This would eliminate the need for guests to compute the software checksum. This series only takes care of virtio net. I have addition patches for the host side (vhost and tap/macvtap as well as qemu), but wanted to get feedback on the general approach first. Vladislav Yasevich (6): virtio-ne...