Messages in this thread | | | Date | Fri, 5 Jun 1998 00:17:46 -0400 (EDT) | From | "Andrew J. Anderson" <> | Subject | Re: alternate /proc/config.gz patch and a kfree question. |
| |
On Fri, 5 Jun 1998, Peter T. Breuer wrote:
> "A month of sundays ago Andrew J. Anderson wrote:" > > > > If the ability to free up that memory after boot is desired, then I > > believe that an implementation similar to mine will need to be used -- I > > did not see any easy way to free up the memory using the array_read style > > entries. > > If you have the heart, please let me have a 2-line synopsis of how you > can free that memory (I'm marking exams and can't do anything else).
With the patch that I submitted, if a write to /proc/config.gz was attempted, it would remove the /proc/config.gz entry and free up the kmalloc'ed memory that held the config.gz information. (See the proc_config_write function in my patch.)
With the static character buffer that the other patch uses, and the fact that it uses the /proc filesystem's array.c to present the data, there is no mechanism that I could find that would allow anything to free up that memory, even if it were dynamically allocated. If I am incorrect in this, please point this out to me.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Andrew Anderson http://amelia.db.erau.edu/~andrew/ if(!(family_tree=fork())){redneck=TRUE;}
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
| |