Sponsored Content
Full Discussion: Memory free() in C
Top Forums Programming Memory free() in C Post 302550703 by alister on Friday 26th of August 2011 06:29:58 PM
Old 08-26-2011
The interface should document memory management responsibilities.
 

10 More Discussions You Might Find Interesting

1. Programming

How to free the memory?

For example if i have the piece of code as follows: CountryName = (char *)malloc((strlen(CountryName)+1)*sizeof(char)); memset(CountryName, 0, strlen(CountryName)+1); CountryName = SOME VALUE Now how do i free the memory after use of this code???? :confused: (3 Replies)
Discussion started by: jazz
3 Replies

2. AIX

Free Memory

Hi, how to find free memory in aix? for installing oracle,I have used svmon but not getting proper output (1 Reply)
Discussion started by: manoj.solaris
1 Replies

3. AIX

Free Memory in aix

Hi, I want to know how to find out free physical memory in aix, (11 Replies)
Discussion started by: manoj.solaris
11 Replies

4. Solaris

How to find Total and Free Physical Memory and Logical Memory in SOLARIS 9

Hi, Im working on Solaris 9 on SPARC-32 bit running on an Ultra-80, and I have to find out the following:- 1. Total Physical Memory in the system(total RAM). 2. Available Physical Memory(i.e. RAM Usage) 3. Total (Logical) Memory in the system 4. Available (Logical) Memory. I know... (4 Replies)
Discussion started by: 0ktalmagik
4 Replies

5. Solaris

how to get the more memory free space (see memory free column)

Hi all, Could please let me know how to get the more memory free space (not added the RAM) in local zone. -bash-3.00# vmstat 2 5 kthr memory page disk faults cpu r b w swap free re mf pi po fr de sr s0 s1 s1 s1 in sy cs us sy... (3 Replies)
Discussion started by: murthy76
3 Replies

6. Red Hat

how to find out free memory?

hi, I have done the below, but am confused as to how much memory is "free" please help thanks $ free total used free shared buffers cached Mem: 132033488 48827536 83205952 0 1007696 45404632 -/+ buffers/cache: 2415208 ... (7 Replies)
Discussion started by: JamesByars
7 Replies

7. UNIX for Advanced & Expert Users

Out of Memory error when free memory size is large

I was running a program and it stopped and showed "Out of Memory!". at that time, the RAM used by this process is around 4G and the free memory size of the machine is around 30G. Does anybody know what maybe the reason? this program is written with Perl. the OS of the machine is Solaris U8. And I... (1 Reply)
Discussion started by: lilili07
1 Replies

8. AIX

How to find AIX Free Memory?

All, AIX: 6.1 64 bits How to find out Free memory available on AIX 6.1 64 bits When I used : svmon -G size inuse free pin virtual mmode memory 1048576 612109 191151 215969 549824 Ded-E pg space 4325376 ... (1 Reply)
Discussion started by: a1_win
1 Replies

9. Solaris

Is there a way to free up memory manually ?

Hi, I am wondering if there is a way to free up memory in Solaris manually ? the way we can do it in Linux for example : echo `/bin/date` "************* Memory Info Before *************" free -m sync echo 1 > /proc/sys/vm/drop_caches echo 2 > /proc/sys/vm/drop_caches echo 3 >... (13 Replies)
Discussion started by: terrykhatri531
13 Replies

10. Solaris

How the free memory threshold?

If I understand your question correctly, you are asking for an explanation of Solaris memory manager. You'd better ask Oracle that question because you are talking about Solaris kernel internals. The operating system kernel has no reason to kick a process's memory set out of real memory until... (4 Replies)
Discussion started by: hicksd8
4 Replies
ddi_fm_handler_register(9F)				   Kernel Functions for Drivers 			       ddi_fm_handler_register(9F)

NAME
ddi_fm_handler_register, ddi_fm_handler_unregister - register or unregister an error handling callback SYNOPSIS
#include <sys/ddifm.h> void ddi_fm_handler_register(dev_info_t *dip, ddi_err_func_t error_handler, void *impl_data); void ddi_fm_handler_unregister(dev_info_t *dip); INTERFACE LEVEL
Solaris DDI specific (Solaris DDI) PARAMETERS
dip Pointer to the dev_info structure error_handler Pointer to an error handler callback function impl_data Pointer to private data for use by the caller DESCRIPTION
The ddi_fm_handler_register() function registers an error handler callback routine with the I/O Fault Management framework. The error han- dler callback, error_handler, is called to process error conditions detected by the system. In addition to its device instance, dip, the error handler is called with a pointer to a fault management error status structure, ddi_fm_error_t. For example: int (*ddi_err_func_t)(dev_info_t *dip, ddi_fm_error_t *error_status); A driver error handling callback is passed the following arguments: o a pointer to the device instance registered for this callback. o a data structure containing common fault management data and status for error handling. The primary responsibilities of the error handler include: o to check for outstanding hardware or software errors. o where possible, to isolate the device that might have caused the errors. o to report errors that were detected. During the invocation of an error handler, a device driver might need to quiesce or suspend all I/O activities in order to check for error conditions or status in: o hardware control and status registers. o outstanding I/O transactions. o access or DMA handles. For each error detected, the driver must formulate and post an error report via ddi_fm_ereport_post() for problem analysis by the Solaris Fault Manager fmd(1M). For a PCI, PCI/X, or PCI Express leaf device, the pci_ereport_post() function is provided to carry out reporting responsibilities on behalf of the driver. In many cases, an error handler callback function of the following form can be used: xxx_err_cb(dev_info_t *dip, ddi_fm_error_t *errp) { pci_ereport_post(dip, errp, NULL); return (errp->fme_status); } In addition, the driver might be able to carry out further device specific checks within the error handler. Error handlers can be called from kernel, interrupt, or high-level interrupt context. The interrupt block cookie returned from ddi_fm_init() should be used to allocate and initialize any synchronization variables and locks that might be used within the error handler callback function. Such locks may not be held by the driver when a device register is accessed with functions such as ddi_get8(9F) and ddi_put8(9F). The data structure, ddi_fm_error_t, contains an FMA protocol (format 1) ENA for the current error propagation chain, the status of the error handler callback, an error expectation flag, and any potential access or DMA handles associated with an error detected by the parent nexus. The ddi_fm_handler_unregister() function removes a previously registered error handling callback for the device instance specified by the dip. CONTEXT
The ddi_fm_handler_register() and ddi_fm_handler_unregister() functions must be called from kernel context in an attach(9E) or detach(9E) entry point. The registered error handler, error_handler, callback can be called from kernel, interrupt, or high level interrupt context. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Committed | +-----------------------------+-----------------------------+ SEE ALSO
fmd(1M), attributes(5), attach(9E), detach(9E), ddi_fm_ereport_post(9F), ddi_fm_init(9F), ddi_get8(9F), ddi_put8(9F), pci_ereport_post(9F), ddi_fm_error(9S) Writing Device Drivers SunOS 5.11 14 May 2007 ddi_fm_handler_register(9F)
All times are GMT -4. The time now is 09:52 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy