[mailto:dev-bounces at dpdk.org] On Behalf Of Venkatesan, Venky
> Sent: Wednesday, August 27, 2014 10:54 PM
> To: dev at dpdk.org
> Subject: Re: [dpdk-dev] overcommitting CPUs
>
> DPDK currently isn't exactly poll mode - it has an API that receives and
> transmits packets. How you
off IRQ until there are a couple packets or a short delay.
> > Going out of poll mode
> > is harder to determine.
> >
> >
> > On Tue, Aug 26, 2014 at 9:59 AM, Zhou, Danny
> > wrote:
> >
> >>
> >> > -Original Message-
> >>
es at dpdk.org] On Behalf Of Stephen Hemminger
>> > Sent: Wednesday, August 27, 2014 12:39 AM
>> > To: Michael Marchetti
>> > Cc: dev at dpdk.org
>> > Subject: Re: [dpdk-dev] overcommitting CPUs
>> >
>> > On Tue, 26 Aug 2014 16:27:1
; parameters.
>> You want to hold off IRQ until there are a couple packets or a short delay.
>> Going out of poll mode
>> is harder to determine.
>>
>>
>> On Tue, Aug 26, 2014 at 9:59 AM, Zhou, Danny wrote:
>>
>>>> -Original Message-
&g
s at dpdk.org] On Behalf Of Stephen Hemminger
> > Sent: Wednesday, August 27, 2014 12:39 AM
> > To: Michael Marchetti
> > Cc: dev at dpdk.org
> > Subject: Re: [dpdk-dev] overcommitting CPUs
> >
> > On Tue, 26 Aug 2014 16:27:14 +
> > "Michael Marchetti&q
l Message-
> > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Stephen Hemminger
> > Sent: Wednesday, August 27, 2014 12:39 AM
> > To: Michael Marchetti
> > Cc: dev at dpdk.org
> > Subject: Re: [dpdk-dev] overcommitting CPUs
> >
> > On Tue, 26 Aug
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Stephen Hemminger
> Sent: Wednesday, August 27, 2014 12:39 AM
> To: Michael Marchetti
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] overcommitting CPUs
>
> On Tue, 26 Aug 2014 1
ailto:dev-bounces at dpdk.org] On Behalf Of Michael Marchetti
> Sent: Wednesday, August 27, 2014 12:27 AM
> To: dev at dpdk.org
> Subject: [dpdk-dev] overcommitting CPUs
>
> Hi, has there been any consideration to introduce a non-spinning network
> driver (interrupt
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) o
On Tue, 26 Aug 2014 16:27:14 +
"Michael Marchetti" 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
10 matches
Mail list logo
