DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: jigsaw <jigsaw@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] Request for comments on ixgbe TSO support
Date: Fri, 4 Oct 2013 14:19:02 -0700	[thread overview]
Message-ID: <20131004141902.710a3f8d@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <CAHVfvh5qF_mjtE_FrgmFUBDLGNOp4rNgbybswr3CPfVKLY5NXw@mail.gmail.com>

On Fri, 4 Oct 2013 22:10:33 +0300
jigsaw <jigsaw@gmail.com> wrote:

> Hi Stephen,
> 
> Thanks for showing a bigger picture.
> 
> GSO is quite big implementation, that I think it won't be easily
> ported to DPDK. The mbuf needs to be equipped with many fields from
> skb to be able to deal with GSO.
> Do you have the plan to port GSO to DPDK, or you would like to keep
> GSO in scope of virtio?
> 
> Regarding checksum flags, actually I was also thinking of extending
> ol_flags but then I gave it up coz I was worried about the size of
> mbuf.
> My current patch has to push some work to user, due to the fact that
> mbuf delivers too few info (such as L2 and L3 protocol details).
> 
> Besides, as you mentioned, the ixgbe driver doesn't leverage the
> hardware receive checksum offloading at all. And if this is to be
> supported, the checksum flag need further extension.
> (On the other hand, TSO doesn't care about receive checksum offloading).
> Again, do you have plans to extend cksum flags so that virio feels
> more comfortable with DPDK?
> 
> Hi Venky,
> 
> I can either make the commit now as is, or wait till the cksum flags
> extension is in place. If Stephen (or somebody else) has the plan for
> better support for cksum offloading or GSO, it is perhaps better to
> implement TSO on top of that.
> 
> BTW, I have another small question. Current TSO patch offloads the
> TCP/IP pseudo cksum work to user. Do you think DPDK could provide some
> utility functions for TCP/IPv4/IPv6 pseudo cksum calculation and
> updating?
> 
> thx &
> rgds,
> -Qinglai

I want to get Tx checksum offload in virtio working first.
Just looking ahead to Rx.

  reply	other threads:[~2013-10-04 21:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-04 17:06 Qinglai Xiao
2013-10-04 17:06 ` [dpdk-dev] [PATCH] ixgbe: TCP/UDP segment offload support on 82599 Qinglai Xiao
2013-10-04 17:40 ` [dpdk-dev] [PATCH] Request for comments on ixgbe TSO support Stephen Hemminger
2013-10-04 17:54   ` jigsaw
2013-10-04 18:23     ` Stephen Hemminger
2013-10-04 18:38       ` Venkatesan, Venky
2013-10-04 19:10         ` jigsaw
2013-10-04 21:19           ` Stephen Hemminger [this message]
2013-10-08  6:59           ` Zhu, Heqing
2013-10-08  7:56             ` jigsaw

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131004141902.710a3f8d@nehalam.linuxnetplumber.net \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=jigsaw@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).