All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.org>
To: "Michael  Marchetti"
	<mmarchetti-oWCY0zUL6IRWk0Htik3J/w@public.gmane.org>
Cc: "dev-VfR2kkLFssw@public.gmane.org" <dev-VfR2kkLFssw@public.gmane.org>
Subject: Re: overcommitting CPUs
Date: Tue, 26 Aug 2014 09:38:37 -0700	[thread overview]
Message-ID: <20140826093837.4e3d1d4b@urahara> (raw)
In-Reply-To: <A7E5BBF1ACE50B43AF1D6E89B8280FE4C5290BB5-optG8WkO7DUmBZHPKbibd5rt+qvZzhbF@public.gmane.org>

On Tue, 26 Aug 2014 16:27:14 +0000
"Michael  Marchetti" <mmarchetti-oWCY0zUL6IRWk0Htik3J/w@public.gmane.org> 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.

  parent reply	other threads:[~2014-08-26 16:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-26 16:27 overcommitting CPUs Michael  Marchetti
     [not found] ` <A7E5BBF1ACE50B43AF1D6E89B8280FE4C5290BB5-optG8WkO7DUmBZHPKbibd5rt+qvZzhbF@public.gmane.org>
2014-08-26 16:38   ` Stephen Hemminger [this message]
2014-08-26 16:59     ` Zhou, Danny
     [not found]       ` <DFDF335405C17848924A094BC35766CF0A90F714-0J0gbvR4kTg/UvCtAeCM4rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-08-27  4:14         ` Stephen Hemminger
     [not found]           ` <CAOaVG178x4DA32XsO8GZCyo5qLKydT0UBo1NO-i-q5roD4VbNw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-08-27  5:48             ` Patel, Rashmin N
     [not found]               ` <C68F1134885B32458704E1E4DA3E34F341A2CFFF-AtyAts71sc9qS6EAlXoojrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-08-27  8:40                 ` Alex Markuze
     [not found]                   ` <CAKfHP0Wpf1scek3yJywmHVDxGOBY6KBDYAZNkcZM0_zqUvt0sw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-08-27 14:54                     ` Venkatesan, Venky
     [not found]                       ` <53FDF11D.3040504-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
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-otpzqlsittunbdjkjebofr2eb7je58tq@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.org \
    --cc=mmarchetti-oWCY0zUL6IRWk0Htik3J/w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.