public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: Jim Nelson <james4765@verizon.net>
To: Ankit Jain <ankitjain1580@yahoo.com>
Cc: newbie <linux-newbie@vger.kernel.org>
Subject: Re: Heavy load of graphics
Date: Tue, 05 Oct 2004 06:04:18 -0400	[thread overview]
Message-ID: <416271A2.8030304@verizon.net> (raw)
In-Reply-To: <20041005050100.76032.qmail@web52902.mail.yahoo.com>

Ankit Jain wrote:

>hi
>
>well i am using linux 9.0 kernel 2.4 ver. 128 Mb RAM
>
>i have seen not only on this sytem but the other one
>having 512 Mb RAM the most of the memory is lost or
>taken by graphics or xserver. on my system around 90%
>is occupied by the xsever and on the sys with 512 Mb
>RAM around 70% is occupied. how to reduce this load. i
>oculd not get any article or stuff relate to this . if
>we can do something in kernel or in some way reduce
>this load while working in GUI envt
>
>thanks
>
>Ankit
>  
>

Could you please post your ps -Al, /proc/meminfo, and lspci output?  I 
know Red Hat has a lot of standard daemons (PCMCIA, ISDN, etc) that are 
started by default - have you used chkconfig or redhat-config-services 
to shut off unneded services?

The kernel also uses a lot of free memory for I/O caching - even my P4 
w/ 1GB RAMBUS shows 90% memory consumption in /proc/meminfo.  Caching is 
a low-priority memory allocation - when the system needs memory for 
active processes, it should give the memory to the process.

BTW, unless you are using a framebuffer kernel-level driver, X is 
handled almost exclusively in userland.  On SPARC32 (for example) 
framebuffers are pretty much the only way to get X working, but mostly, 
XFree86 and the X.org server that comes with FC2 use mostly user-space 
drivers.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" 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.linux-learn.org/faqs

  parent reply	other threads:[~2004-10-05 10:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-05  5:01 Heavy load of graphics Ankit Jain
2004-10-05  5:45 ` Jeff Woods
2004-10-05  6:34 ` Ray Olszewski
2004-10-05  9:25 ` Geert Uytterhoeven
2004-10-05 10:04 ` Jim Nelson [this message]
2004-10-06  6:35   ` Ankit Jain
2004-10-06 21:02     ` Jim Nelson
2004-10-07 12:48       ` Ankit Jain
2004-10-07 22:00         ` Jim Nelson
2004-10-07 22:04         ` chuck gelm
2004-10-08  5:27           ` Ankit Jain
2004-10-08 14:37             ` Ray Olszewski
2004-10-05 12:26 ` chuck gelm
2004-10-05 16:25 ` Terrence Martin
2004-10-06  4:55   ` Ankit Jain
2004-10-07  1:50     ` chuck gelm
2004-10-07  2:07 ` Peter
2004-10-07  5:48   ` Ray Olszewski
2004-10-07  6:25     ` Owen Ford
2004-10-07 12:14   ` Ankit Jain

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=416271A2.8030304@verizon.net \
    --to=james4765@verizon.net \
    --cc=ankitjain1580@yahoo.com \
    --cc=linux-newbie@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox