mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Neil Horman <nhorman@redhat.com>
To: "Márcio Oliveira" <moliveira@latinsourcetech.com>
Cc: arjanv@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: Memory Management
Date: Thu, 21 Jul 2005 09:11:32 -0400	[thread overview]
Message-ID: <20050721131132.GB11327@hmsendeavour.rdu.redhat.com> (raw)
In-Reply-To: <42DF9646.5070806@latinsourcetech.com>

On Thu, Jul 21, 2005 at 09:34:14AM -0300, Márcio Oliveira wrote:
> Arjan van de Ven wrote:
> 
> >On Wed, 2005-07-20 at 11:23 -0300, Márcio Oliveira wrote:
> > 
> >
> >>Arjan van de Ven wrote:
> >>
> >>   
> >>
> >>>I'm sure RH support will be able to help you with that; I doubt many
> >>>other people care about an ancient kernel like that, and a vendor one to
> >>>boot.
> >>>
> >>>(Also I assume you are using the -hugemem kernel as the documentation
> >>>recommends you to do)
> >>>
> >>>
> >>>
> >>>     
> >>>
> >>Arjan,
> >>
> >>  I'd like to know/understand more about memory management  on  Linux 
> >>Kernel and I belive this concept is applyable to the Red Hat Linux Kernel.
> >>   
> >>
> >
> >Only on the highest of levels. The RHEL3 kernel has a VM that resembles
> >almost no other linux kernel in many many ways. 
> >
> >
> > 
> >
> >> I have some doubts about the ZONE divison (DMA, NORMAL, HIGHMEM), 
> >>Shared Memory utilization, HugeTLB feature and OOM with large memory and 
> >>the kernel management of memory on SMP machines. I believe these 
> >>features are common to the Linux kernel in general(Red Hat, Debian, 
> >>SuSe, kernel.org), right?
> >>   
> >>
> >
> >nope. These things are very much different between the kernels you
> >mention.
> >
> >What do you want to use the knowledge for? Fixing the VM? Tuning your
> >server? The goal of your question determines what kind of answer you
> >want to your questions....
> > 
> >
> It's about tunning the VM parameters...
> 
> That's my first question on list:
> 
> "Is HugeTBL proc memory parameters only to hugetlbfs "filesystem" or are 
> these parameters affect ramfs, shm and tmpfs too?
> 
> What is the basic difference between ramfs, hugetlbfs, shm and tmpfs to 
> the memory management / process VLM utilization?
> 
> thanks,
> 
http://people.redhat.com/nhorman/papers/rhel3_vm.pdf
I wrote this with norm awhile back.  It may help you out.
Regards
Neil

> Márcio."
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
/***************************************************
 *Neil Horman
 *Software Engineer
 *Red Hat, Inc.
 *nhorman@redhat.com
 *gpg keyid: 1024D / 0x92A74FA1
 *http://pgp.mit.edu
 ***************************************************/

  reply	other threads:[~2005-07-21 13:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-21 12:34 Márcio Oliveira
2005-07-21 13:11 ` Neil Horman [this message]
2005-07-21 13:40   ` Márcio Oliveira
2005-07-22 14:02     ` Neil Horman
2005-07-22 14:32       ` Márcio Oliveira
2005-07-22 19:08         ` Neil Horman
2005-07-22 19:41           ` Márcio Oliveira
2005-07-22 20:58             ` Roger Heflin
2005-07-22 23:23               ` Márcio Oliveira
2005-07-23 18:45                 ` Neil Horman
2005-07-23 23:16                   ` Márcio Oliveira
2005-07-24 18:54                     ` Neil Horman
2005-07-25  1:40                       ` Márcio Oliveira
2005-07-25  9:47                         ` Seiji Kihara
2005-07-25 14:30                         ` Neil Horman
2005-07-25 17:04                           ` Márcio Oliveira
  -- strict thread matches above, loose matches on Subject: below --
2005-07-20 13:10 Memoy Management Márcio Oliveira
2005-07-20 13:24 ` Arjan van de Ven
2005-07-20 14:23   ` Memory Management Márcio Oliveira
2005-07-20 14:37     ` Arjan van de Ven

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=20050721131132.GB11327@hmsendeavour.rdu.redhat.com \
    --to=nhorman@redhat.com \
    --cc=arjanv@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=moliveira@latinsourcetech.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

all inboxes | Powered by JetHome®