Re: [Xen-devel] credit2 data structures

>>> On 13.10.11 at 12:57, Keir Fraser <keir@xxxxxxx> wrote:
> On 13/10/2011 11:11, "George Dunlap" <George.Dunlap@xxxxxxxxxxxxx> wrote:
> 
>> For one thing, the number of runqueues in credit2 is actually meant to
>> be smaller than the number of logical cpus -- it's meant to be one per
>> L2 cache, which should have between 2 and 8 logical cpus, depending on
>> the architecture.  I just put NR_CPUS because it was easier to get
>> working.  Making that an array of pointers, which is allocated on an
>> as-needed basis, should reduce that requirement a great deal.
> 
> That would suffice. If we can put per-cpu stuff in the per_cpu() data area
> then even better.

That might not be possible, as there can be more than one instance of
that scheduler.

> The fact that credit2 burns a couple of kB per CPU isn't a
> problem at all, as long as it does it only for active CPUs.

Fully agree.

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread]

Current Thread

[Next in Thread>

Previous by Date:

Re: [Xen-devel] [PATCH] xenpaging: check p2mt in p2m_mem_paging functions, Olaf Hering

Next by Date:

Re: [Xen-devel] why xen use x86_emulation() in page_fault, Christoph Egger

Previous by Thread:

Re: [Xen-devel] credit2 data structures, Keir Fraser

Next by Thread:

Re: [Xen-devel] credit2 data structures, Jan Beulich

Indexes:

[Date] [Thread] [Top] [All Lists]