DPDK patches and discussions
 help / color / mirror / Atom feed
From: Alexander Belyakov <abelyako@gmail.com>
To: 吴亚东 <wuyd@outlook.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK testpmd forwarding performace degradation
Date: Tue, 27 Jan 2015 11:04:26 +0300	[thread overview]
Message-ID: <CAAQJX_SksjCZxgg0vqhLEuqc8OiSPKxJMZuRk6_-uEW6OF8v1Q@mail.gmail.com> (raw)
In-Reply-To: <BAY176-W12D96351C9C7B97C488C96C3320@phx.gbl>

Hello,

On Tue, Jan 27, 2015 at 5:49 AM, 吴亚东 <wuyd@outlook.com> wrote:

> 65 bytes frame may degrade performace a lot.Thats related to DMA and cache.
> When NIC dma packets to memory, NIC has to do read modify write if DMA
> size is partial cache line.So for 65 bytes, the first 64 bytes are ok. The
> next 1 byte NIC has to read the whole cache line, change one byte and
> update the cache line.
> So in DPDK, CRC is not stripped and ethernet header aligned to cache line
> which causes ip header not aligned on 4 bytes.
>
>
Extra cache line update indeed makes sense because performance is halved
with extra byte.

It is a little bit confusing, but the issue is not with switching from 64
bytes frames to 65 bytes frames, but with switching from 80 bytes frame to
81 bytes frame. Note that the issue disappears at 96 bytes frame size.

Alexander

  reply	other threads:[~2015-01-27  8:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-27  2:49 吴亚东
2015-01-27  8:04 ` Alexander Belyakov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-01-26 10:17 Alexander Belyakov
2015-01-26 14:22 ` De Lara Guarch, Pablo
     [not found]   ` <CAAQJX_RueTvfr7UnANbLSKceerkfs5DZNguKdPhSVVn9OCGtrw@mail.gmail.com>
2015-01-27  7:51     ` [dpdk-dev] Fwd: " Alexander Belyakov
2015-01-27 10:14       ` [dpdk-dev] " Alexander Belyakov
2015-01-27 16:21         ` De Lara Guarch, Pablo
2015-01-28 12:24           ` Alexander Belyakov
2015-01-29 12:43             ` Alexander Belyakov
2015-02-05 14:39               ` Alexander Belyakov
2015-01-26 17:08 ` Stephen Hemminger

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=CAAQJX_SksjCZxgg0vqhLEuqc8OiSPKxJMZuRk6_-uEW6OF8v1Q@mail.gmail.com \
    --to=abelyako@gmail.com \
    --cc=dev@dpdk.org \
    --cc=wuyd@outlook.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).