Andi Kleen wrote:
> On Fri, Feb 22, 2008 at 05:44:47PM +0530, Balbir Singh wrote:
>> My concern with all the points you mentioned is that this solution might
>> need to
>> change again,
>
> No why would it need to change again?
>
>> depending on the factors you've mentioned. vmalloc() is good an
On Fri, Feb 22, 2008 at 05:44:47PM +0530, Balbir Singh wrote:
>
> My concern with all the points you mentioned is that this solution might need
> to
> change again,
No why would it need to change again?
> depending on the factors you've mentioned. vmalloc() is good and
> straightforward, but it
Andi Kleen wrote:
> Balbir Singh wrote:
>> Andi Kleen wrote:
1. We could create something similar to mem_map, we would need to handle 4
>>> 4? At least x86 mainline only has two ways now. flatmem and vmemmap.
>>>
different ways of creating mem_map.
>>> Well it would be only a single way t
Balbir Singh wrote:
> Andi Kleen wrote:
>>> 1. We could create something similar to mem_map, we would need to handle 4
>> 4? At least x86 mainline only has two ways now. flatmem and vmemmap.
>>
>>> different ways of creating mem_map.
>> Well it would be only a single way to create the "aux memory c
KAMEZAWA Hiroyuki wrote:
> On Thu, 21 Feb 2008 16:33:33 +0530
> Balbir Singh <[EMAIL PROTECTED]> wrote:
>
>>> Another issue is that it will slightly increase TLB/cache
>>> cost of the memory controller, but I think that would be a fair
>>> trade off for it being zero cost when disabled but compile
On Thu, 21 Feb 2008 16:33:33 +0530
Balbir Singh <[EMAIL PROTECTED]> wrote:
> > Another issue is that it will slightly increase TLB/cache
> > cost of the memory controller, but I think that would be a fair
> > trade off for it being zero cost when disabled but compiled
> > in.
> >
> > Doing it wit
Andi Kleen wrote:
>> 1. We could create something similar to mem_map, we would need to handle 4
>
> 4? At least x86 mainline only has two ways now. flatmem and vmemmap.
>
>> different ways of creating mem_map.
>
> Well it would be only a single way to create the "aux memory controller
> map" (or
On Wednesday 20 February 2008 23:52, Balbir Singh wrote:
> Andi Kleen wrote:
> > Document huge memory/cache overhead of memory controller in Kconfig
> >
> > I was a little surprised that 2.6.25-rc* increased struct page for the
> > memory controller. At least on many x86-64 machines it will not fi
Hi
> > I think one reason of many people easy confusion is caused by bad menu
> > hierarchy.
> > I popose mem-cgroup move to child of cgroup and resource counter
> > (= obey denend on).
>
> > +config CGROUP_MEM_CONT
> > + bool "Memory controller for cgroups"
>
> Memory _resource_ controller fo
Hi!
> > > >> For ordinary desktop people, memory controller is what developers
> > > >> know as MMU or sometimes even some other mysterious piece of silicon
> > > >> inside the heavy box.
> > > >
> > > >Actually I'd guess 'memory controller' == 'DRAM controller' == part of
> > > >northbridge
KOSAKI Motohiro wrote:
> Hi
>
>> > >> For ordinary desktop people, memory controller is what developers
>> > >> know as MMU or sometimes even some other mysterious piece of silicon
>> > >> inside the heavy box.
>> > >
>> > >Actually I'd guess 'memory controller' == 'DRAM controller' == part o
Hi
> > >> For ordinary desktop people, memory controller is what developers
> > >> know as MMU or sometimes even some other mysterious piece of silicon
> > >> inside the heavy box.
> > >
> > >Actually I'd guess 'memory controller' == 'DRAM controller' == part of
> > >northbridge that talks t
Andi Kleen wrote:
> Nick Piggin wrote:
>> On Wednesday 20 February 2008 23:52, Balbir Singh wrote:
>>> Andi Kleen wrote:
Document huge memory/cache overhead of memory controller in Kconfig
I was a little surprised that 2.6.25-rc* increased struct page for the
memory controller.
> 1. We could create something similar to mem_map, we would need to handle 4
4? At least x86 mainline only has two ways now. flatmem and vmemmap.
> different ways of creating mem_map.
Well it would be only a single way to create the "aux memory controller
map" (or however it will be called). Ba
Nick Piggin wrote:
> On Wednesday 20 February 2008 23:52, Balbir Singh wrote:
>> Andi Kleen wrote:
>>> Document huge memory/cache overhead of memory controller in Kconfig
>>>
>>> I was a little surprised that 2.6.25-rc* increased struct page for the
>>> memory controller. At least on many x86-64 m
KAMEZAWA Hiroyuki wrote:
> On Wed, 20 Feb 2008 21:45:13 +0530
> Balbir Singh <[EMAIL PROTECTED]> wrote:
>
>>> But for computers, limits is an expected and understood term, and for
>>> filesystems it's quotas. So in this case, I *still* think you should
>>> be using the term "Memory Quota Controll
On Wed, 20 Feb 2008 21:45:13 +0530
Balbir Singh <[EMAIL PROTECTED]> wrote:
> > But for computers, limits is an expected and understood term, and for
> > filesystems it's quotas. So in this case, I *still* think you should
> > be using the term "Memory Quota Controller" instead. It just makes it
Nick Piggin wrote:
>> 1. We could create something similar to mem_map, we would need to handle 4
>
>> different ways of creating mem_map.
>
>> 2. On x86 with 64 GB ram, if we decided to use vmalloc space, we would need
>
>> 64 MB of vmalloc'ed memory
>
> That's going to be a big job. You could
Nick Piggin wrote:
> On Wednesday 20 February 2008 23:52, Balbir Singh wrote:
>> Andi Kleen wrote:
>>> Document huge memory/cache overhead of memory controller in Kconfig
>>>
>>> I was a little surprised that 2.6.25-rc* increased struct page for the
>>> memory controller. At least on many x86-64 m
On Wed 2008-02-20 19:28:03, Jan Engelhardt wrote:
>
> On Feb 20 2008 18:19, Pavel Machek wrote:
> >>
> >> For ordinary desktop people, memory controller is what developers
> >> know as MMU or sometimes even some other mysterious piece of silicon
> >> inside the heavy box.
> >
> >Actually I'd gues
On Feb 20 2008 18:19, Pavel Machek wrote:
>>
>> For ordinary desktop people, memory controller is what developers
>> know as MMU or sometimes even some other mysterious piece of silicon
>> inside the heavy box.
>
>Actually I'd guess 'memory controller' == 'DRAM controller' == part of
>northbridge
Hi!
> >> I know this is a pedantic comment, but why the heck is it called such
> >> a generic term as "Memory Controller" which doesn't give any
> >> indication of what it does.
> >>
> >> Shouldn't it be something like "Memory Quota Controller", or "Memory
> >> Limits Controller"?
> >
> >It's cal
> OK, I'll queue a patch and try to explain various terms used by resource
> management.
Don't make it too verbose or nobody will read it. It should
be more like a one paragraph abstract on a scientific paper
about the linux memory controller.
But I think it should include some variant of the w
> I know this is a pedantic comment, but why the heck is it called such
> a generic term as "Memory Controller" which doesn't give any
> indication of what it does.
I don't think it's pedantic. I would agree with you in fact
that the Kconfig description is not very helpful, even with
my warning a
On Wed, Feb 20, 2008 at 7:20 AM, Balbir Singh <[EMAIL PROTECTED]> wrote:
> John Stoffel wrote:
> > I know this is a pedantic comment, but why the heck is it called such
> > a generic term as "Memory Controller" which doesn't give any
> > indication of what it does.
> >
> > Shouldn't it be some
John Stoffel wrote:
>> "Jan" == Jan Engelhardt <[EMAIL PROTECTED]> writes:
>
> Jan> On Feb 20 2008 20:50, Balbir Singh wrote:
>>> John Stoffel wrote:
I know this is a pedantic comment, but why the heck is it called such
a generic term as "Memory Controller" which doesn't give any
>>>
> "Balbir" == Balbir Singh <[EMAIL PROTECTED]> writes:
Balbir> John Stoffel wrote:
>> I know this is a pedantic comment, but why the heck is it called such
>> a generic term as "Memory Controller" which doesn't give any
>> indication of what it does.
>>
>> Shouldn't it be something like "Memo
> "Jan" == Jan Engelhardt <[EMAIL PROTECTED]> writes:
Jan> On Feb 20 2008 20:50, Balbir Singh wrote:
>> John Stoffel wrote:
>>> I know this is a pedantic comment, but why the heck is it called such
>>> a generic term as "Memory Controller" which doesn't give any
>>> indication of what it does.
On Feb 20 2008 20:50, Balbir Singh wrote:
>John Stoffel wrote:
>> I know this is a pedantic comment, but why the heck is it called such
>> a generic term as "Memory Controller" which doesn't give any
>> indication of what it does.
>>
>> Shouldn't it be something like "Memory Quota Controller", or
John Stoffel wrote:
> I know this is a pedantic comment, but why the heck is it called such
> a generic term as "Memory Controller" which doesn't give any
> indication of what it does.
>
> Shouldn't it be something like "Memory Quota Controller", or "Memory
> Limits Controller"?
>
It's called th
> "Balbir" == Balbir Singh <[EMAIL PROTECTED]> writes:
Balbir> Andi Kleen wrote:
>> Document huge memory/cache overhead of memory controller in Kconfig
>>
>> I was a little surprised that 2.6.25-rc* increased struct page for the memory
>> controller. At least on many x86-64 machines it will
Andi Kleen wrote:
> Document huge memory/cache overhead of memory controller in Kconfig
>
> I was a little surprised that 2.6.25-rc* increased struct page for the memory
> controller. At least on many x86-64 machines it will not fit into a single
> cache line now anymore and also costs considerab
Document huge memory/cache overhead of memory controller in Kconfig
I was a little surprised that 2.6.25-rc* increased struct page for the memory
controller. At least on many x86-64 machines it will not fit into a single
cache line now anymore and also costs considerable amounts of RAM.
At earli
33 matches
Mail list logo
