From: Dave Taht <dave.taht@gmail.com>
To: avatli@itu.edu.tr
Cc: "codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>
Subject: Re: [Codel] Codel on DPDK
Date: Tue, 18 Oct 2016 08:43:18 -0700 [thread overview]
Message-ID: <CAA93jw73+t4cwyMqwxh-M8eooRCcTPxXabp1+zXf4=hJd3o0Dg@mail.gmail.com> (raw)
In-Reply-To: <20161018144234.Horde.G87Yvb-Fv8vOgZa1kd0MXA1@webmail.itu.edu.tr>
On Tue, Oct 18, 2016 at 4:42 AM, <avatli@itu.edu.tr> wrote:
> Hello
>
> I'm trying to implement CoDel-like implementation on Intel's DPDK library,
> but I have trouble with measuring packet sojourn time on RX/TX queues
> because of DMA usage. When I call send() function, DPDK puts the packets
> into DMA-region and I have no idea when the packets sent really into
> network. Likewise, when I call recv(), I don't have any idea when the
> packets arrived, so I'm not sure totally but I think I have no chance to
> measure sojourn time for dma-like implementation. Could you please correct
> me if I'm wrong. Also any comments/suggestions would be greatly appreciated.
I am under the impression there is a dpdk implementation already, somewhere.
As for the amount of time things spend in dma, you are hopefully
talking about a few mere
us, and the default for codel is only worrying about ms, so you can do
the codel work before the send and after the recv.
> Thanks in advance..
>
> - Volkan
>
>
> _______________________________________________
> Codel mailing list
> Codel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/codel
>
--
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org
next prev parent reply other threads:[~2016-10-18 15:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 11:42 avatli
2016-10-18 15:43 ` Dave Taht [this message]
2016-10-18 15:44 ` Dave Taht
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
List information: https://lists.bufferbloat.net/postorius/lists/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw73+t4cwyMqwxh-M8eooRCcTPxXabp1+zXf4=hJd3o0Dg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=avatli@itu.edu.tr \
--cc=codel@lists.bufferbloat.net \
/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