From: Eric Dumazet <eric.dumazet@gmail.com>
To: Chetan Loke <chetanloke@gmail.com>
Cc: Bhavesh Davda <bhavesh@vmware.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"pv-drivers@vmware.com" <pv-drivers@vmware.com>,
"therbert@google.com" <therbert@google.com>
Subject: Re: [Pv-drivers] rps and pvdrivers
Date: Sat, 04 Sep 2010 08:51:35 +0200 [thread overview]
Message-ID: <1283583095.2320.11.camel@edumazet-laptop> (raw)
In-Reply-To: <AANLkTi=o8GYdLyY8EzfRno39O2kUSh3wSp9raZCUp_Zz@mail.gmail.com>
Le vendredi 03 septembre 2010 à 18:39 -0400, Chetan Loke a écrit :
> Hi Bhavesh,
>
> On Fri, Sep 3, 2010 at 5:05 PM, Bhavesh Davda <bhavesh@vmware.com> wrote:
>
> >
> > I presume you're talking about the vmxnet3 vNIC here? What version of the VMware hypervisor are you observing this with? Could you share the vmware.log (and potentially the vmkernel log) file from the VM where you're seeing this?
> >
>
> Yes its vmxnet3 on esx 4.1. I've attached the vm-log file. Its easy to
> reproduce - A simple 'rcvfrom' loop on a promiscuous interface.
>
>
Reproduce what exactly ?
I dont understand what the problem is, reading your description.
RPS is not automatically switched on, you have to configure it.
echo ffff >/sys/class/net/eth0/queues/rx-0/rps_cpus
Same for RFS if you prefer to use RFS
echo 16384 >/sys/class/net/eth0/queues/rx-0/rps_flow_cnt
If you receive a flood, your cpu stay in NAPI mode, and no hardware
interrupt is received while you process xxx.xxx packets per second.
next prev parent reply other threads:[~2010-09-04 6:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 19:49 rps and pvdrivers Chetan Loke
2010-09-03 21:05 ` [Pv-drivers] " Bhavesh Davda
2010-09-03 22:39 ` Chetan Loke
2010-09-04 6:51 ` Eric Dumazet [this message]
2010-09-04 7:00 ` Eric Dumazet
2010-09-04 13:38 ` Chetan Loke
2010-09-04 13:51 ` Eric Dumazet
2010-09-04 14:02 ` Chetan Loke
2010-09-04 14:31 ` Eric Dumazet
2010-09-04 15:27 ` Chetan Loke
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=1283583095.2320.11.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=bhavesh@vmware.com \
--cc=chetanloke@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pv-drivers@vmware.com \
--cc=therbert@google.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