From: Thomas Monjalon <thomas@monjalon.net>
To: Ilya Matveychikov <matvejchikov@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] A question about (poor) rte_ethdev internal rx/tx callbacks design
Date: Sun, 12 Nov 2017 03:43:19 +0100 [thread overview]
Message-ID: <10275972.2udXxazxJp@xps> (raw)
In-Reply-To: <2259E047-80C0-40AC-AAF4-F21617605508@gmail.com>
11/11/2017 18:18, Ilya Matveychikov:
> Folks,
>
> Are you serious with it:
No, DPDK is not serious, just a hobby for few crazy folks ;)
Usually, we have fun discussions when someone explains clearly an issue.
Please do not hesitate to bring your lights,
we will check how seriously we can improve.
next prev parent reply other threads:[~2017-11-12 2:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-11 17:18 Ilya Matveychikov
2017-11-12 2:43 ` Thomas Monjalon [this message]
2017-11-13 10:39 ` Adrien Mazarguil
2017-11-13 10:56 ` Ilya Matveychikov
2017-11-13 17:15 ` Adrien Mazarguil
2017-11-13 19:33 ` Ilya Matveychikov
2017-11-14 6:24 ` Andrew Rybchenko
2017-11-13 10:58 ` Ananyev, Konstantin
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=10275972.2udXxazxJp@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=matvejchikov@gmail.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).