From: Matthew Hall <mhall@mhcomputing.net>
To: Cody Doucette <doucette@bu.edu>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] filtering IPv6 packets in hardware
Date: Tue, 27 Sep 2016 12:29:16 -0700 [thread overview]
Message-ID: <20160927192916.GA1997@mhcomputing.net> (raw)
In-Reply-To: <CAJjX64ZTUX2q1R0PmeBit6Oh7hLgp9nYto3KT9Dhq+D8NsH5=w@mail.gmail.com>
On Tue, Sep 27, 2016 at 12:06:25PM -0400, Cody Doucette wrote:
> Has anyone encountered this problem before? Any tips on how I could make
> this work -- or even suggestions for better hardware?
In general these problems are very commonplace among the community members. We
have had many painful discussions on these topics since you only get 9.6
nanoseconds and only so many opcodes to handle each new frame.
>From the software side the distributor framework could help.
>From the hardware side you have to read all of the data sheets for the chips
supported by each PMD to find the chip with the right features for your use
case.
> Thanks!
> Cody
Matthew.
next prev parent reply other threads:[~2016-09-27 19:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 16:06 Cody Doucette
2016-09-27 19:29 ` Matthew Hall [this message]
2016-09-28 6:58 ` Mcnamara, John
2016-09-28 16:16 ` Cody Doucette
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=20160927192916.GA1997@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=doucette@bu.edu \
--cc=users@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).