DPDK patches and discussions
 help / color / mirror / Atom feed
From: Daniel Kaminsky <daniel.kaminsky@infinitelocality.com>
To: chen_lp <chen_lp@neusoft.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] 82599 TX IP checksum offloading
Date: Mon, 25 Nov 2013 11:15:31 +0200	[thread overview]
Message-ID: <CA+8v-Jyhc78B0kMrjeKe1SnD_z4MHS38uGvnAaBmA6WAHCwY8A@mail.gmail.com> (raw)
In-Reply-To: <5292ECDB.6070007@neusoft.com>

chen_Ip,

You shoudln't use PKT_RX_IPV4_HDR, either just PKT_TX_IP_CKSUM or some
other combination of PKT_TX_* (e.g. PKT_TX_OFFLOAD_MASK)

Daniel


On Mon, Nov 25, 2013 at 8:23 AM, chen_lp <chen_lp@neusoft.com> wrote:

> Hi,
> I want NIC to calculate ip checksum on dpdk-1.5.0,
>
> I have set:
> static const struct rte_eth_txconf tx_conf = {
>         .tx_thresh = {
>                 .pthresh = TX_PTHRESH,
>                 .hthresh = TX_HTHRESH,
>                 .wthresh = TX_WTHRESH,
>         },
>         .tx_free_thresh = 0,
>         .tx_rs_thresh = 0,
>         .txq_flags = 0,
> };
> this struct is used by int rte_eth_tx_queue_setup(uint8_t port_id,
> uint16_t tx_queue_id,
>                                   uint16_t nb_tx_desc, unsigned int
> socket_id,
>                                   const struct rte_eth_txconf **tx_conf*);
>
> when constructing the pkt will been sending:
>
> mbuf->ol_flags|=(PKT_TX_IP_CKSUM|PKT_RX_IPV4_HDR);
>                                            |~
> mbuf->pkt.vlan_macip.f.l2_len = sizeof(struct ether_hdr);
>                                             |~
> mbuf->pkt.vlan_macip.f.l3_len = sizeof(struct ipv4_hdr);
>
>
> but the NIC not calculate ip checksum,did anyone tell me what's wrong
> whith it?
> by the way,I create multi-queue for tx and rx.
>
>
> Thanks,
> chen_lp
>
>
> ---------------------------------------------------------------------------------------------------
> Confidentiality Notice: The information contained in this e-mail and any
> accompanying attachment(s)
> is intended only for the use of the intended recipient and may be
> confidential and/or privileged of
> Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader
> of this communication is
> not the intended recipient, unauthorized use, forwarding, printing,
>  storing, disclosure or copying
> is strictly prohibited, and may be unlawful.If you have received this
> communication in error,please
> immediately notify the sender by return e-mail, and delete the original
> message and all copies from
> your system. Thank you.
>
> ---------------------------------------------------------------------------------------------------
>

      reply	other threads:[~2013-11-25  9:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-25  6:23 chen_lp
2013-11-25  9:15 ` Daniel Kaminsky [this message]

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=CA+8v-Jyhc78B0kMrjeKe1SnD_z4MHS38uGvnAaBmA6WAHCwY8A@mail.gmail.com \
    --to=daniel.kaminsky@infinitelocality.com \
    --cc=chen_lp@neusoft.com \
    --cc=dev@dpdk.org \
    /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).