From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] ixgbe: fix check for split packets
Date: Wed, 22 Jul 2015 15:47:10 +0200 [thread overview]
Message-ID: <2646761.JxpPTaGeqc@xps13> (raw)
In-Reply-To: <59AF69C657FD0841A61C55336867B5B03457D2BE@IRSMSX103.ger.corp.intel.com>
2015-07-22 13:35, Richardson, Bruce:
> From: Zoltan Kiss [mailto:zoltan.kiss@linaro.org]
> > On 22/07/15 10:59, Bruce Richardson wrote:
> > > The vector PMD always works off a fixed 32 burst size. Any change to
> > > that will lead to many changes in the code, so I don't believe a loop is
> > necessary.
> >
> > Ok, then I suggest to make a comment around RTE_IXGBE_VPMD_RX_BURST that
> > changing it needs a lot of other changes in the code elsewhere, e.g in
> > this split_flags check.
> > Btw. vPMD was a bit misleading abbreviation for me, it took me a while
> > until I realized 'v' stands for 'vector', not 'virtualization' as in most
> > cases nowadays.
>
> Good idea. I'll try to submit a patch to add a comment if I get the chance
> - otherwise feel free to do so yourself.
Why not do it in this patch?
Is it not enough related?
> As for the naming, yes, I suppose it can be confusing. :-) We possibly need
> to start calling these pieces of code SSE or AVX rather than just vector,
> since for some we may end up with multiple vector versions.
+1 for SSE/AVX naming
next prev parent reply other threads:[~2015-07-22 13:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 15:25 [dpdk-dev] [PATCH] " Bruce Richardson
2015-07-22 0:44 ` Lu, Wenzhuo
2015-07-22 8:29 ` Bruce Richardson
2015-07-22 9:13 ` [dpdk-dev] [PATCH v2] " Bruce Richardson
2015-07-22 9:47 ` Zoltan Kiss
2015-07-22 9:59 ` Bruce Richardson
2015-07-22 13:19 ` Zoltan Kiss
2015-07-22 13:22 ` Zoltan Kiss
2015-07-22 13:35 ` Richardson, Bruce
2015-07-22 13:47 ` Thomas Monjalon [this message]
2015-07-26 12:41 ` Thomas Monjalon
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=2646761.JxpPTaGeqc@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=bruce.richardson@intel.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).