DPDK usage discussions
 help / color / mirror / Atom feed
From: ankit bhardwaj <ankitbhrdwj27@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Fwd: How to change the batch size at NIC
Date: Thu, 23 Mar 2017 09:03:24 +0530	[thread overview]
Message-ID: <CAC4R1nkdN+BVVUV521H0LNjv3wpWMu48C57MtREL__HDCFkH9A@mail.gmail.com> (raw)
In-Reply-To: <CAC4R1nmGZgUgiqt_XQjoz1mwXuegFGT0ZBzRijy0mGXVkwam3w@mail.gmail.com>

Hello All,

I have two NICs in my server, intel x520 and x540. I am interested in
performance(throughput) of the application when we change the batching
factor at NIC and in application.


I can change the batch size in the DPDK application, but I am not sure how
to do at the NIC. What needs to be changed in the code to change the batch
size at NIC and what is the default batch size at NIC in DPDK ?


Thanks,
Ankit Bhardwaj

           reply	other threads:[~2017-03-23  3:33 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAC4R1nmGZgUgiqt_XQjoz1mwXuegFGT0ZBzRijy0mGXVkwam3w@mail.gmail.com>]

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=CAC4R1nkdN+BVVUV521H0LNjv3wpWMu48C57MtREL__HDCFkH9A@mail.gmail.com \
    --to=ankitbhrdwj27@gmail.com \
    --cc=users@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).