From: kumaraparameshwaran rathinavel <kumaraparamesh92@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: hujiayu.hu@foxmail.com, dev@dpdk.org
Subject: Re: [PATCH] lib/gro: use hash function for flow lookup
Date: Thu, 2 Jan 2025 09:23:06 +0530 [thread overview]
Message-ID: <CANxNyavxMCkOmdgB19_jKTjBqooUrBqhoTTdSBjk8m=8H9-N_g@mail.gmail.com> (raw)
In-Reply-To: <20250101092138.4fb5fdee@fedora>
[-- Attachment #1: Type: text/plain, Size: 1171 bytes --]
On Wed, Jan 1, 2025 at 10:51 PM Stephen Hemminger <
stephen@networkplumber.org> wrote:
> On Wed, 1 Jan 2025 15:07:35 +0530
> Kumara Parameshwaran <kumaraparamesh92@gmail.com> wrote:
>
> > From: Kumara Parameshwaran <kumaraparamesh92@gmail.com>
> > To: hujiayu.hu@foxmail.com
> > Cc: dev@dpdk.org, Kumara Parameshwaran <kumaraparamesh92@gmail.com>
> > Subject: [PATCH] lib/gro: use hash function for flow lookup
> > Date: Wed, 1 Jan 2025 15:07:35 +0530
> > X-Mailer: git-send-email 2.47.1
> >
> > optimize the GRO lookup using hash based
> > implementation
> >
> > Signed-off-by: Kumara Parameshwaran <kumaraparamesh92@gmail.com>
>
> Rather than open coding a hash table with collision chains, please use the
> existing DPDK cuckoo hash which is faster and you can also prevent hash
> DoS chain attacks.
> >>Sure, I was thinking to use cuckoo hash, but then thought if this could
> be an overkill to for this implementation.
> Alternatively, use a better hash function such as siphash which is
> resistent
> to DoS attacks.
>> Yes, sure. Will change it. Had used that to get an idea for the
overall implementation itself.
>
[-- Attachment #2: Type: text/html, Size: 2338 bytes --]
prev parent reply other threads:[~2025-01-02 3:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-01 9:37 Kumara Parameshwaran
2025-01-01 17:21 ` Stephen Hemminger
2025-01-02 3:53 ` kumaraparameshwaran rathinavel [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='CANxNyavxMCkOmdgB19_jKTjBqooUrBqhoTTdSBjk8m=8H9-N_g@mail.gmail.com' \
--to=kumaraparamesh92@gmail.com \
--cc=dev@dpdk.org \
--cc=hujiayu.hu@foxmail.com \
--cc=stephen@networkplumber.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).