RSS Feeds56 results. Narrow Selection By Tag Memory AND
Other:
- Kernel
- Administration - Bela - CPU - Code - Disks/Filesystems - Drivers
- FAQ - Install/Upgrade - Performance - Programming - Unix - Unix Words
- Kernel
- Administration - Bela - CPU - Code - Disks/Filesystems - Drivers
- FAQ - Install/Upgrade - Performance - Programming - Unix - Unix Words
vhand plowbufs tuning configure memory low buffers-->VHAND PLOWBUFS Re I can't find something!
PLOWBUFs is a percentage- so 5% of 1 gig is 50,000,000 etc. Is there some reason why you didn't drop it to one- nowadays there's not much you'd need low buffers for anyway (these are for things that need DMAable memory)..
| Title | Date | Comments | |||
|---|---|---|---|---|---|
| A Nonvolatile Memory Overview | 2004 10 | 2012/05/28 TonyLawrence | |||
| - This paper presents a basic nonvolatile memory (NVM) overview. Section I begins with the introduction including a brief background of NVM's and the common terms used in the memory industry. The description and explanation of how an NVM is programmed (adding electrons) using hot-carrier injection is covered in section II. Section III covers the erasing or removing of electrons from floating gates of NVM's. A brief mechanism of Fowler-Nordheim tunneling is covered. Section IV introduces the model that can be used to predict the NVM programming characteristics. The hot-carrier injection model addressed is the "Lucky Electron" model. Section V covers the reliability aspects of NVM's. The common reliability issues an NVM encounters are the data retention, endurance, and disturbs. - | |||||
| Where's the memory? | 2006 06 | ||||
| - Memory usage under Linux is full of surprises. Do not assume you know what's going on based upon your knowledge of other systems. - | |||||
| Adding Memory | 2007 10 | ||||
| - Adding RAM to your computer - how-to and pictures. Nowadays we need more and more RAM. If you have Windows boxes, you know that 512MB is becoming bare minimum, the same is true for Macs and although Linux can get by with less, more is better.. - | |||||
| Understanding memhog -->Re memhog/u386mon/ps Why the differences? | 1997-2004 | ||||
| - The sizes reported by memhog are in system pages (4K). The vsize column is the size (in pages) of the virtual address space for the process. All the other columns are real memory pages. - | |||||
| allocb failed NSTRPAGES exceeded streams memory netstat -m-->Re I can't find something! | 1997-2004 | ||||
| - You are running out of streams memory- run "netstat -m"- you'll likely see non-zero amounts in the Failures column. - | |||||
| shmget ipcs shared memory -->Re Memory error relating toshmget | 1997-2004 | ||||
| - shmget ipcs shared memory -->Re: Memory error relating toshmget - | |||||
| Memory leaks | 2005 12 | ||||
| - I don't do any C programming any more, but I certainly remember that tracking down memory allocation problems was a large part of my debugging work. Obviously I'm not the only one who makes such programming errors; a Google search in that area will turn up all kinds of tools and debuggers to help track these things down. - | |||||
| bootlocore : out of low memory | 2005 06 | ||||
| - bootlocore : out of low memory SCO Unix No memory for relocation information - | |||||
| Memory | 2003 10 | ||||
| - Under normal conditions, one Unix process has absolutely no access to another's memory. However, sometimes it can be helpful (for reasons of speed, usually) to be able to read or write a shared memory area. Therefore, Unix and Linux systems provide system calls to setup and use such areas. - | |||||
| Adding Memory | 1999 03 | ||||
| - Adding Memory to SCO Unix, tuning NBUF and NHBUF to use that RAM - | |||||
| showmem- shows contents of memory pages | 1997 12 | ||||
| - Unix Programs: showmem script dumps memory from /dev/mem to show contents of dual ported ram - | |||||
| My system is slow or hangs when sizing memory | 1997-2003 | ||||
| - This is an old article about memory caching on SCO Unix and is only left here for historical purposes. - | |||||
 | |||||
| I have a system memory dump in my swap space; how do I delete it? | 1997-2003 | ||||
| - I have a system memory dump in my swap space; how do Idelete i - | |||||
| linux memory gtop -->Re Memory clean up | 1997-2004 | ||||
| - Linux tries to never have much idle memory linux memory gtop -->Re: Memory clean up - | |||||
| uw7 unixware 7 kernel memory tuning rtpm -->Re Unixware7.1 memory | 1997-2004 | ||||
| - uw7 unixware 7 kernel memory tuning rtpm -->Re: Unixware7.1 memory - | |||||
| vhand plowbufs tuning configure memory low buffers-->VHAND PLOWBUFS Re I can't find something! | 1997-2004 | ||||
| - vhand spinning on sco OSR5 - configuring PLOWBUFS (DMA buffers) - | |||||
| clearing memory -->Re Memory purge | 1997-2004 | ||||
| - clearing memory -->Re: Memory purge - | |||||
| vhand -->Re free-memory analysis, Re vhand runaway onQuad PIII | 1997-2004 | ||||
| - vhand -->Re: free-memory analysis, Re: vhand runaway onQuad PIII - | |||||
| slow system out of memory swapping -->Re What is causingmy server to page? | 1997-2004 | ||||
| - slow system out of memory swapping -->Re: What is causingmy server to page? - | |||||
| trubleshooting data file corruption testing disks memory-->Re How to trouble-shoot file corruption? | 1997-2004 | ||||
| - If you don't have the space, you have to take running snapshots with fuser or lsof- that may not satisfy a very stubborn vendor who is convinced that *their* programs never screw up. - | |||||
| maximum size of virtual memory -->Re MAXIMUM SIZE OFVIRTUAL MEMORY ? | 1997-2004 | ||||
| - maximum size of virtual memory -->Re: MAXIMUM SIZE OFVIRTUAL MEMORY ? - | |||||
| vhand large memory 4 GB 4GB -->Re vhand | 1997-2004 | ||||
| - vhand large memory 4 GB 4GB -->Re: vhand - | |||||
| old sco version memory mem= | 1997-2004 | ||||
| - old sco version memory mem= - | |||||
| linux out of vm virtual memory -->Re VM Killing process.... | 1997-2004 | ||||
| - To survive this, the kernel goes into lifesaver mode and begins "reaping" processes somewhat randomly in order to free memory so that it won't crash. (I think the only process safe from reaping is probably init). 0 - | |||||
| Confusing kernel memory map OSR5 kernel memory (SCO Unix) | 1997-2004 | ||||
| - It's additionally confusing to throw these all out in a single table, interleaved with the unused areas, and show a summation below which only sums some of the lines! - | |||||
| maximum memory 512mb OSR5.0.2 | 1997-2004 | ||||
| - maximum memory 512mb OSR5.0.2 - | |||||
| samba memory leak | 1997-2004 | ||||
| - One thread includes a reply from a Samba developer saying 'I'm applying the change to all branches.', so this is presumably fixed in the current CVS of Samba 2.2.x. - | |||||
| running out of memory, swapping | 1997-2004 | ||||
| - running out of memory, swapping - | |||||
| vhand determining PLOWBUFS used, DMA memory available-->free-memory analysis, Re vhand runaway on Quad PIII[possible FAQ material] | 1997-2004 | ||||
| - vhand: determining PLOWBUFS used - | |||||
| system load display tool -->Re System / Disk / CPU /Memory load tool | 1997-2004 | ||||
| - system load display tool -->Re: System / Disk / CPU /Memory load tool - | |||||
| system load display tool -->Re System / Disk / CPU /Memory load tool | 1997-2004 | ||||
| - system load display tool -->Re: System / Disk / CPU /Memory load tool - | |||||
| malloc memory bounds purify compiler -->Re malloc coredump | 1997-2004 | ||||
| - malloc memory bounds purify compiler -->Re: malloc coredump - | |||||
| slow system out of memory swapping -->Re What is causingmy server to page? | 1997-2004 | ||||
| - slow system out of memory swapping -->Re: What is causingmy server to page? - | |||||
| available memory -->Re Memory Problem | 1997-2004 | ||||
| - available memory -->Re: Memory Problem - | |||||
| available memory -->Re Memory Problem | 1997-2004 | ||||
| - available memory -->Re: Memory Problem - | |||||
| available memory -->Re Memory Problem | 1997-2004 | ||||
| - available memory -->Re: Memory Problem - | |||||
| cpu memory cache l1 l2 -->Re memory issues | 1997-2004 | ||||
| - When you access a certain point in RAM, it is presumed that the next access will be to an adjacent location. So those adjacent locations get transferred to cache on the assumption that they'll soon be needed. - | |||||
| 4GB ram 4 GB memory -->Re 4Gb's of Ram on Server | 1997-2004 | ||||
| - 4GB ram 4 GB memory -->Re: 4Gb's of Ram on Server - | |||||
| 5.0.0 memory limits -->Re How much memory is support bySCO OPENSERVER 5.0.0d | 1997-2004 | ||||
| - 5.0.0 memory limits -->Re: How much memory is support bySCO OPENSERVER 5.0.0d - | |||||
| bootlocore out of low memory -->Re bootlocore out oflow (below 1Mb) memory! when trying to boot up from bootdisk | 1997-2004 | ||||
| - Check BIOS setup. Many systems allow you to set the low memory area to either 512K or 640K, make sure it's 640K. If there are any other settings which decrease the below-1MB area, disable them as well. The process of boot-time loading a driver needs a lot of low memory. - | |||||
| nbuf memory cache NBUFS -->Re Does 5.0.6 support morethan 450000 NBUF? | 1997-2004 | ||||
| - nbuf memory cache NBUFS -->Re: Does 5.0.6 support morethan 450000 NBUF? - | |||||
| nbuf memory cache NBUFS -->Re Does 5.0.6 support morethan 450000 NBUF? | 1997-2004 | ||||
| - nbuf memory cache NBUFS -->Re: Does 5.0.6 support morethan 450000 NBUF? - | |||||
| dual ported ram device driver virtual memory physical memory-->Re KERNEL PANIC when my Device Driver accesseshardware | 1997-2004 | ||||
| - Programming driver for dual port ram; virtual addresses vs. physical - | |||||
| unixware MAXLINK -->Re HELP!! ERROR Out of memoryInsufficient or invalid memory | 1997-2004 | ||||
| - unixware MAXLINK -->Re: HELP!! ERROR: Out of memory:Insufficient or invalid memory - | |||||
| unixware MAXLINK -->Re HELP!! ERROR Out of memoryInsufficient or invalid memory | 1997-2004 | ||||
| - unixware MAXLINK -->Re: HELP!! ERROR: Out of memory:Insufficient or invalid memory - | |||||
| memory holes -->Re OS5.x and BIOS memory holes at15-16M | 1997-2004 | ||||
| - memory holes -->Re: OS5.x and BIOS memory holes at15-16M - | |||||
| memory sco 5.0.2 -->Re memory | 1997-2004 | ||||
| - memory sco 5.0.2 -->Re: memory - | |||||
| performance tuning sar nhbufs memory -->Re Performancequestion | 1997-2004 | ||||
| - performance tuning sar nhbufs memory -->Re: Performancequestion - | |||||
| linux memory gtop -->Re Memory clean up | 1997-2004 | ||||
| - linux memory gtop -->Re: Memory clean up - | |||||
| uw7 unixware 7 kernel memory tuning rtpm -->Re Unixware7.1 memory | 1997-2004 | ||||
| - uw7 unixware 7 kernel memory tuning rtpm -->Re: Unixware7.1 memory - | |||||
 | |||||
| uw7 unixware 7 kernel memory tuning rtpm -->Re Unixware7.1 memory | 1997-2004 | ||||
| - uw7 unixware 7 kernel memory tuning rtpm -->Re: Unixware7.1 memory - | |||||
| linux cron -->Re strange behavior in my cron job | 1997-2004 | ||||
| - linux cron -->Re: strange behavior in my cron job - | |||||
| linux shared memory -->Re 2.4.0-test and lack of sharedmemory | 1997-2004 | ||||
| - linux shared memory -->Re: 2.4.0-test and lack of sharedmemory - | |||||
| linux memory -->Re What's to do with too much RAM? | 1997-2004 | ||||
| - Why was old Linux only using 64MB of ram? It wasn't a kernel limit; it was old machine bioses. - | |||||
| linux vm virtual memory -->Re UVM virtual memory algorithm | 1997-2004 | ||||
| - linux vm virtual memory -->Re: UVM virtual memoryalgorithm - | |||||
| memory leak or recursive loop -->Re Netscape memoryleak | 1997-2004 | ||||
| - Identifying memory leaks and recursive code with "crash" (SCO Unix) - | |||||
 | |||||
