From: Rami Rosen <ramirose@gmail.com>
To: Shirley Avishour <shirley@imvisiontech.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] running dpdk application on the same machine with other none dpdk application
Date: Wed, 30 Jan 2019 08:09:26 +0200 [thread overview]
Message-ID: <CAHLOa7TP_Qrm2aDdAQT=MpS-1Fs+DtCGe8PQpxFXdtH6AU4cEQ@mail.gmail.com> (raw)
In-Reply-To: <CACn717hahpyEHZsj+xrSFwLEEvgSWHbQnMsdcrsLZvAYQSNuwg@mail.gmail.com>
Hi, Shirley
>In order to do that we isolated the dpdk application cores and disabled
hyperthreading for those cores.
>we are using 5 cores for the dpdk application (which is in fact 10 since
hyperthreading is disabled).
Short clarification question: did you do it with EAL paramater ?
Was it with
-l CORELIST / --lcores COREMAP EAL parameter ?
Did you try also the isolcpus Linux kernel parameter in order to isolate
cores from the general Linux scheduler?
Regards,
Rami Rosen
On Tue, Jan 29, 2019 at 6:32 PM Shirley Avishour <shirley@imvisiontech.com>
wrote:
> Hi,
> We are trying to run a dpdk based application one the same machine with
> other java based applications.
> In order to do that we isolated the dpdk application cores and disabled
> hyperthreading for those cores.
> But sporadically we encounter misses over the interface.
> We are running on a single socket cpu with 44 hyperthreaded cores.
> we are using 5 cores for the dpdk application (which is in fact 10 since
> hyperthreading is disabled).
> My guess is that probably GC (garbage collection) running from the kernel
> and perhaps over the isolated threads causing the misses.
> Is there a way to solve this issue? Is there a way to isolate cores for
> kernel processes/threads?
> Thanks in advance,
> Shirley.
>
--
regards,
Rami Rosen
next prev parent reply other threads:[~2019-01-30 6:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 16:32 Shirley Avishour
2019-01-30 6:09 ` Rami Rosen [this message]
2019-01-30 6:31 ` Shirley Avishour
2019-01-30 6:57 ` Rami Rosen
2019-01-30 7:05 ` Shirley Avishour
2019-01-30 7:26 ` Rami Rosen
2019-01-30 7:47 ` Shirley Avishour
2019-01-30 8:18 ` Rami Rosen
2019-01-30 8:27 ` Shirley Avishour
2019-01-30 8:30 ` Shirley Avishour
2019-01-30 8:40 ` Rami Rosen
2019-01-30 8:45 ` Shirley Avishour
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='CAHLOa7TP_Qrm2aDdAQT=MpS-1Fs+DtCGe8PQpxFXdtH6AU4cEQ@mail.gmail.com' \
--to=ramirose@gmail.com \
--cc=dev@dpdk.org \
--cc=shirley@imvisiontech.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).