From: Cheng Kevin <k5896246@gmail.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] DPDK testpmd, Virtual Disk IO limitation
Date: Thu, 26 Mar 2015 00:20:42 +0800 [thread overview]
Message-ID: <CACnuE8GYK2E4LELuCsAdRChWViOY6jYLBYXA9AdGd4Bn9u8ZHw@mail.gmail.com> (raw)
In-Reply-To: <20150325150156.GA5620@bricha3-MOBL3>
Mr. Bruce Richardson
Yes, you are right. This really bother me.
Is there any way to get rid of system call? Maybe some DPDK threading API?
Maybe i should use a extra nic card for posting the data out through
internet, instead of writing on the disk - ex. fwrite.
Or you have some better advises??
Thanks
Kevin
2015-03-25 23:01 GMT+08:00 Bruce Richardson <bruce.richardson@intel.com>:
> On Wed, Mar 25, 2015 at 10:06:48PM +0800, Cheng Kevin wrote:
> > Hi all,
> >
> > I am a beginner of DPDK. Recently, i am interest in DPDK vHost app -
> > testpmd.
> >
> > And i have been tracing on testpmd.c and iofwd.c for a while.
> >
> > Also add some code inside iofwd.c for storing the payload of packets.
> >
> > Everything goes fine, and the performance is great as expected.
> >
> > But when i use fwrite to store the payload into a file,
> >
> > the performance decrease from 800mbps to 3mbps (input stream is 1
> Gbps).
> >
> > Is is caused by the limitation of Virtual Disk IO? How can i solve it?
> >
> > I have tried to search the answer, some people say "pthread" might
> solve
> > the problem.
> >
> > Can someone give me some hint, i really appreciate for your help.
> >
> >
> > Best Regard,
> >
> > Kevin Cheng
>
> Two general issues you will hit writing to disk:
> 1) IO, including disk IO, is slow
> 2) System calls are slow.
>
> You are probably hitting both bottlenecks.
>
> /Bruce
>
next prev parent reply other threads:[~2015-03-25 16:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 14:06 Cheng Kevin
2015-03-25 15:01 ` Bruce Richardson
2015-03-25 16:20 ` Cheng Kevin [this message]
2015-03-25 17:32 ` Bruce Richardson
2015-03-25 23:47 ` Cheng Kevin
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=CACnuE8GYK2E4LELuCsAdRChWViOY6jYLBYXA9AdGd4Bn9u8ZHw@mail.gmail.com \
--to=k5896246@gmail.com \
--cc=bruce.richardson@intel.com \
--cc=dev@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).