[OpenAFS-devel] AFSD memory footprint

[Neulinger, Nathan]

I think that'll probably depend on which os/kernel. Depends on whether the
o/s will de-allocate when unused.

There might be another option - what about forking itself and passing the
limited info needed, and then terminating the process that did all the
allocations? (Not sure if this is feasible, just an idea.)

-- Nathan

> -----Original Message-----
> From: Derek Atkins [mailto:warlord@MIT.EDU]
> Sent: Thursday, August 02, 2001 1:29 PM
> To: openafs-devel@openafs.org
> Subject: [OpenAFS-devel] AFSD memory footprint
> 
> 
> So, afsd winds up mallocing a lot of memory during it's cache sweep
> and startup stages.  I don't think it needs most of that memory by the
> time it calls into the kernel.  Is there any reason that we don't
> 'free()' that memory before the last afs_syscall()?  I'm thinking that
> this could potentially free a few megabytes of RAM.  Or will it not
> matter since the virtual memory is already mapped into the process
> space?
> 
> -derek
> -- 
>        Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
>        Member, MIT Student Information Processing Board  (SIPB)
>        URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
>        warlord@MIT.EDU                        PGP key available
> _______________________________________________
> OpenAFS-devel mailing list
> OpenAFS-devel@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-devel
>