Linux Today: Linux News On Internet Time.
Search Linux Today
search.internet.com
Linux News Sections:  Blog -  Developer -  High Performance -  Infrastructure -  IT Management -  Security -  Storage -
Linux Today Navigation
LT Home
Preferences
Contribute
Link to Us
Search
Linux Jobs

Become a Marketplace Partner

internet.commerce
Be a Commerce Partner














The Linux Channel at internet.com
Linux Today
Enterprise Linux Today
Apache Today
JustLinux.com
Linux Planet
PHPBuilder
All Linux Devices
Technology Jobs

JustTechJobs.com

LinuxToday Newsletters
Subscribe News
Subscribe PR
Subscribe Security

internet.com
IT
Developer
Internet News
Small Business
Personal Technology

Search internet.com
Advertise
Corporate Info
Newsletters
Tech Jobs
E-mail Offers

 






Current Newswire:

Mastering Grub 2 The Easy Way

Shedding commercial attitudes towards documentation

Will secret copyright treaty restrict your digital rights?

Saving the "Best" for Last - Fedora 12 (Constantine)

LinuxCertified Announces its next Linux System and Network Administration BootCamp

The Problem With The Linux Community

Vim 101: A Beginner's Guide to Vim

Open Source Science: A Revolution From Within

openSUSE 11.2-- Incremental Updates, Plenty of Polish

Microsoft, other rivals slam Google Chrome OS




UNIX System Administrator - SUN Solaris, Veritas, EMC, Shell Scripting, SAN (NYC)
Next Step Systems
US-NY-New York

Justtechjobs.com Post A Job | Post A Resume
:Kernel Space: Memory Allocation Failures
Kernel Space: Memory Allocation Failures
Apr 17, 2008, 06 :00 UTC (0 Talkback[s]) (3895 reads)

(Other stories by Jonathan Corbet)

"In general, the kernel's memory allocator does not like to fail. So, when kernel code requests memory, the memory management code will work hard to satisfy the request. If this work involves pushing other pages out to swap or removing data from the page cache, so be it. A big exception happens, though, when an atomic allocation (using the GFP_ATOMIC flag) is requested. Code requesting atomic allocations is generally not in a position where it can wait around for a lot of memory housecleaning work; in particular, such code cannot sleep. So if the memory manager is unable to satisfy an atomic allocation with the memory it has in hand, it has no choice except to fail the request.

"Such failures are quite rare, especially when single pages are requested. The kernel works to keep some spare pages around at all times, so the memory stress must be severe before a single-page allocation will fail..."

Complete Story

Related Stories:
Kernel Space: Toward Better Direct I/O Scalability(Apr 14, 2008)
Kernel Space: ELF Prediction to Speed Application Startup(Apr 06, 2008)
Kernel Space: Authoritative Hooks for Containerization(Mar 27, 2008)
Kernel Space: How to Use a Terabyte of RAM(Mar 20, 2008)



No talkbacks posted.
  Home | Search Talkbacks | Customize View    Top of Page  



Enter your comments below:

* Your Name:

* Your Email Address:

* Subject:

CC: [will also send this talkback to an E-Mail address]

* Comments:

Tags allowed:<I>,<B> and <U>. See our talkback-policy for more about talkback content.

Fields marked with * are required!






..............................




All times are recorded in UTC.
Linux is a trademark of Linus Torvalds.
Powered by Linux, Apache and PHP

internet.commediabistro.comJusttechjobs.comGraphics.com

Search:

WebMediaBrands Corporate Info

Legal Notices, Licensing, Permissions, Privacy Policy.
Advertise | Newsletters | Shopping | E-mail Offers | Freelance Jobs