DPDK patches and discussions
 help / color / mirror / Atom feed
From: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Hayato Momma <h-momma@ce.jp.nec.com>
Subject: Re: [dpdk-dev] [memnic PATCH 1/7] guest: memnic-tester: PMD benchmark in guest
Date: Wed, 24 Sep 2014 23:54:19 +0000	[thread overview]
Message-ID: <7F861DC0615E0C47A872E6F3C5FCDDBD02AD9DD6@BPXM14GP.gisp.nec.co.jp> (raw)
In-Reply-To: <9049135.zKavqy3ols@xps13>

Hi,
> Subject: Re: [dpdk-dev] [memnic PATCH 1/7] guest: memnic-tester: PMD benchmark in guest
> 
> Hi Hiroshi,
> 
> 2014-09-11 07:46, Hiroshi Shimamoto:
> >  master |<- put packets ->|     |<- get packets ->|
> >  slave  |   |<- rx packets ->|<- tx packets ->|   |
> >         |<----------------- set ----------------->|
> >
> > Measuring how many sets in the certain period, that represents
> > the MEMNIC PMD performance. The master workload must be very low.
> 
> Sorry, I don't really understand this diagram and the associated explanation.
> Could you try to reword it?

sure, will make more understandable description.
Could you please help me to do that?

The purpose of this program is measuring the performance of MEMNIC PMD itself.
It means that we'd like to know how much the PMD takes in rx and tx API.
The program does rx and tx in the slave thread and the PMD performance could
be measured how much packets are handled in certain period. By the way we
need to fill and clear MEMNIC packet buffer for enabling to work the PMD rx/tx
in the slave thread. Then, I made the master thread which fills and clears
MEMNIC packet buffer in the lightest way, and it should be with the least jitter.
If we generate a real packet out of VM, that may cause increasing jitter
outside of the MEMNIC PMD, it means we will not see the precise performance
of MEMNIC PMD itself.

Can you see the concept of this benchmark with the above?

thanks,
Hiroshi

> 
> Thanks
> --
> Thomas

  reply	other threads:[~2014-09-24 23:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-11  7:46 Hiroshi Shimamoto
2014-09-24 15:10 ` Thomas Monjalon
2014-09-24 23:54   ` Hiroshi Shimamoto [this message]
2014-09-25  9:02     ` 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=7F861DC0615E0C47A872E6F3C5FCDDBD02AD9DD6@BPXM14GP.gisp.nec.co.jp \
    --to=h-shimamoto@ct.jp.nec.com \
    --cc=dev@dpdk.org \
    --cc=h-momma@ce.jp.nec.com \
    --cc=thomas.monjalon@6wind.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).