BPF List
 help / color / mirror / Atom feed
From: Taehee Yoo <ap420073@gmail.com>
To: Igor Russkikh <irusskikh@marvell.com>,
	davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	netdev@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	hawk@kernel.org, john.fastabend@gmail.com, andrii@kernel.org,
	kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
	kpsingh@kernel.org, bpf@vger.kernel.org
Subject: Re: [EXT] [PATCH net-next v4 0/3] net: atlantic: Add XDP support
Date: Wed, 13 Apr 2022 18:59:49 +0900	[thread overview]
Message-ID: <805b4f95-5351-b342-7177-6a3df979be17@gmail.com> (raw)
In-Reply-To: <dac72406-2743-ce1a-a0d7-4078e5d222be@marvell.com>

2022. 4. 13. 오후 4:52에 Igor Russkikh 이(가) 쓴 글:

Hi Igor,

Thank you so much for your review!

 >
 >
 >> v4:
 >>   - Fix compile warning
 >>
 >> v3:
 >>   - Change wrong PPS performance result 40% -> 80% in single
 >>     core(Intel i3-12100)
 >>   - Separate aq_nic_map_xdp() from aq_nic_map_skb()
 >>   - Drop multi buffer packets if single buffer XDP is attached
 >>   - Disable LRO when single buffer XDP is attached
 >>   - Use xdp_get_{frame/buff}_len()
 >
 > Hi Taehee, thanks for taking care of that!
 >
 > Reviewed-by: Igor Russkikh <irusskikh@marvell.com>
 >
 > A small notice about the selection of 3K packet size for XDP.
 > Its a kind of compromise I think, because with common 1.4K MTU we'll 
get wasted
 > 2K bytes minimum per packet.
 >
 > I was thinking it would be possible to reuse the existing page 
flipping technique
 > together with higher page_order, to keep default 2K fragment size.
 > E.g.
 > ( 256(xdp_head)+2K(pkt frag) ) x 3 (flips) = ~7K
 >
 > Meaning we can allocate 8K (page_order=1) pages, and fit three xdp 
packets into each, wasting only 1K per three packets.
 >
 > But its just kind of an idea for future optimization.
 >

Yes, I fully agree with your idea.
When I developed an initial version of this patchset, I simply tried 
that idea.
I expected to reduce CPU utilization(not for memory optimization), but 
there is no difference because page_ref_{inc/dec}() cost is too high.
So, if we tried to switch from MEM_TYPE_PAGE_ORDER0 to 
MEM_TYPE_PAGE_SHARED, I think we should use a littie bit different 
flipping strategy like ixgbe.
If so, we would achieve memory optimization and CPU optimization.

Thanks a lot,
Taehee Yoo

 > Regards,
 >    Igor

      reply	other threads:[~2022-04-13 10:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08 18:17 [PATCH net-next v4 0/3] net: atlantic: Add XDP support Taehee Yoo
2022-04-08 18:17 ` [PATCH net-next v4 1/3] net: atlantic: Implement xdp control plane Taehee Yoo
2022-04-08 18:17 ` [PATCH net-next v4 2/3] net: atlantic: Implement xdp data plane Taehee Yoo
2022-04-08 18:17 ` [PATCH net-next v4 3/3] net: atlantic: Implement .ndo_xdp_xmit handler Taehee Yoo
2022-04-12  7:17 ` [PATCH net-next v4 0/3] net: atlantic: Add XDP support Paolo Abeni
2022-04-13  7:52 ` [EXT] " Igor Russkikh
2022-04-13  9:59   ` Taehee Yoo [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=805b4f95-5351-b342-7177-6a3df979be17@gmail.com \
    --to=ap420073@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=hawk@kernel.org \
    --cc=irusskikh@marvell.com \
    --cc=john.fastabend@gmail.com \
    --cc=kafai@fb.com \
    --cc=kpsingh@kernel.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=songliubraving@fb.com \
    --cc=yhs@fb.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