> Should we make a new configure option to allow us to change the default size? > Should we just make the change to the library? Are there other > issues/concerns with changing this type?
I don't have a problem increasing this to 16 or even 32 bits. What is the output of sizeof(DofObject) with the different options? It is possible that some of the choices result in the same size on a particular architecture because of padding concerns. I would suggest we just make the change in the library. If someone really wants to limit the memory footprint of their installation they are better off disabling AMR, the subdomain_id type is much more in the noise. (If we really want to get fancy we could pack the number of systems and the subdomain id type into the first entry of the DofObject's indices array. We only need 8 bits for n_sys, you can have 24 for the subdomain type!) -Ben ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
