From: Stephen Hemminger <stephen@networkplumber.org>
To: "Michael Marchetti" <mmarchetti@sandvine.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] overcommitting CPUs
Date: Tue, 26 Aug 2014 09:38:37 -0700 [thread overview]
Message-ID: <20140826093837.4e3d1d4b@urahara> (raw)
In-Reply-To: <A7E5BBF1ACE50B43AF1D6E89B8280FE4C5290BB5@wtl-exchp-1.sandvine.com>
On Tue, 26 Aug 2014 16:27:14 +0000
"Michael Marchetti" <mmarchetti@sandvine.com> wrote:
> Hi, has there been any consideration to introduce a non-spinning network driver (interrupt based), for the purpose of overcommitting CPUs in a virtualized environment? This would obviously have reduced high-end performance but would allow for increased guest density (sharing of physical CPUs) on a host.
>
> I am interested in adding support for this kind of operation, is there any interest in the community?
>
> Thanks,
>
> Mike.
Better to implement a NAPI like algorithm that adapts from poll to interrupt.
next prev parent reply other threads:[~2014-08-26 16:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 16:27 Michael Marchetti
2014-08-26 16:38 ` Stephen Hemminger [this message]
2014-08-26 16:59 ` Zhou, Danny
2014-08-27 4:14 ` Stephen Hemminger
2014-08-27 5:48 ` Patel, Rashmin N
2014-08-27 8:40 ` Alex Markuze
2014-08-27 14:54 ` Venkatesan, Venky
2014-08-28 4:03 ` Liang, Cunming
2014-08-27 16:06 ` Zhou, Danny
2014-08-26 16:42 ` Zhou, Danny
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=20140826093837.4e3d1d4b@urahara \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=mmarchetti@sandvine.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).