LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 10-01-2011, 08:31 PM   #1
SlackBuddy
LQ Newbie
 
Registered: Sep 2011
Posts: 4

Rep: Reputation: Disabled
Memory Mnagement


How does Slackware handle its memory or how does it allocate memory properly? are their any bugs in memory management?
 
Click here to see the post LQ members have rated as the most helpful post in this thread.
Old 10-01-2011, 08:49 PM   #2
Ian John Locke II
Member
 
Registered: Mar 2008
Location: /dev/null
Distribution: Slackware, Android, Slackware64
Posts: 130

Rep: Reputation: 17
I can't answer your first question but I can tell that slackware has one of the smallest memory footprints I've ever seen (for an operating system).
 
Old 10-01-2011, 10:26 PM   #3
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 4,650

Rep: Reputation: 1770Reputation: 1770Reputation: 1770Reputation: 1770Reputation: 1770Reputation: 1770Reputation: 1770Reputation: 1770Reputation: 1770Reputation: 1770Reputation: 1770
It's not Slackware's job to handle the memory. It's the kernel you are talking about
 
2 members found this post helpful.
Old 10-02-2011, 12:40 AM   #4
SlackBuddy
LQ Newbie
 
Registered: Sep 2011
Posts: 4

Original Poster
Rep: Reputation: Disabled
Oh, I'm sorry. So how, does the kernel in Slackware handles memory?

---------- Post added 10-02-11 at 05:41 AM ----------

Why have you say that Slackware has smallest memory?
 
Old 10-02-2011, 01:10 AM   #5
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,858

Rep: Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225Reputation: 2225
http://linux-mm.org/
 
2 members found this post helpful.
Old 10-02-2011, 02:14 AM   #6
ponce
LQ Guru
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 7,060

Rep: Reputation: 4139Reputation: 4139Reputation: 4139Reputation: 4139Reputation: 4139Reputation: 4139Reputation: 4139Reputation: 4139Reputation: 4139Reputation: 4139Reputation: 4139
also, your kernel sources tree got a nice folder named "Documentation" that can be useful too.
 
2 members found this post helpful.
Old 10-02-2011, 11:33 AM   #7
Ian John Locke II
Member
 
Registered: Mar 2008
Location: /dev/null
Distribution: Slackware, Android, Slackware64
Posts: 130

Rep: Reputation: 17
Well I've run slack with a start-up size of about 60 MB while I've seen ubuntu and other distros start up around 110 MB using the same WM. And I use the default install too with the exception of using dwm or wmii which each have smaller sizes than kde or gnome it xfce

Also I've seen debian start up around 65 or 70 LB. It's partially why I prefer both to other distributions

Last edited by Ian John Locke II; 10-02-2011 at 11:35 AM.
 
1 members found this post helpful.
Old 10-03-2011, 07:56 AM   #8
storkus
Member
 
Registered: Jun 2008
Location: Phoenix, Arizona, USA
Distribution: Slackware
Posts: 329

Rep: Reputation: 51
On my machine, I have traditionally compiled my own kernel as one of the first steps on a new install of Slackware. I hadn't done it in a few years, but went and did it this time around again. Con: It takes literally SEVERAL HOURS to go through all the menus and (de)select the various options. Pros: far smaller memory footprint AND things are noticeably snappier--even on the TurionX2 in my laptop; you'll see even better results on older hardware.

Another thing to consider on total memory footprint are the various daemons running: in addition, turning off daemons ("services" in winblows-speak) is also a very security-conscious thing to do. (Now I just need to figure out how to chroot-jail ntpd one of these days...)

If you're REALLY hardcore, only install software, libraries, and drivers you know you'll actually use. I used to do this, but it mostly doesn't make sense anymore on non-embedded hardware; OTOH, it may make sense to remove crap you don't need X to use since it usually auto-loads it (drivers, fonts, etc) into memory.

Bear in mind that, in most cases, your biggest memory hogs will be X (after running for a while, it doesn't like to release memory for some reason), graphical web browsers, and big, fat window manager systems, which normally means KDE on Slackware. XFCE is getting a little plump now, too, but having the extra icons and other bells and whistles on reasonably modern hardware overcomes the limitations of running FVWM2 with its tiny footprint, IMHO. Of course, YMMV.

I hope this helps. Of course, if you're thinking of going embedded and you like the Slackware way of doing things, Linux From Scratch has instructions to help you give it more slack; the down side is that you don't benefit from the experience of Pat and his boys getting even unstable software to seemingly run reliably, a feat that I marvel at to this day.
 
Old 10-04-2011, 01:44 PM   #9
Ian John Locke II
Member
 
Registered: Mar 2008
Location: /dev/null
Distribution: Slackware, Android, Slackware64
Posts: 130

Rep: Reputation: 17
I have to agree with storkus. I didn't do it on my last installation but even so I feel like it's a leaner installation than a "default" installation of most other distros (unless you start doing netinstalls and don't install much afterwards).

In my case, the things I use the most are:
gcc
python
X
firefox
wmii
vim/gvim

And of those, firefox takes the most memory, then X. wmii should take more memory than the rest depending on what else I'm running but that's only because it's a window manager that's pretty damned fast and slick. As light weight as it is, it isn't for everyone. Openbox and blackbox (and really any *box) window managers are good for lightweight and highly customizable window managers.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Error while saving memory pages of a process- Sleeping in memory from invalid context Deep Narayan Dubey Linux - Kernel 1 04-05-2012 02:58 PM
Memory leaks.. *** glibc detected *** ./SuffixTree: malloc(): memory corruption: 0x00 evansash Programming 12 03-21-2011 01:17 PM
Difference between resident memory,shared memory and virtual memory in system monitor mathimca05 Linux - Newbie 1 11-11-2007 04:05 AM
Help!?! RH 8 Memory Mapping -High Memory-Virtural Memory issues.. Merlin53 Linux - Hardware 2 06-18-2003 04:48 PM
RH 8.0 Mapping Virtual Memory to get access to VMIC Reflective Memory PCI card. Merlin53 Linux - Hardware 0 05-05-2003 12:50 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 12:43 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration