Hi Krishna This is very interesting work. I wonder what EAP method was used for authentication? Did you make any efforts to reduce the RAM consumption or was this simply the standard supplicant package (can you also write the version information)?. An interesting thing to know is the idle memory consumption (when the supplicant is simply running as a daemon) and the peak memory consumption (which I guess is during authentication and re-keying) Thanks Khali On Mon, Jun 20, 2016 at 12:32 PM, Krishna Chaitanya <chaitanya.mgit@xxxxxxxxx> wrote: > On Mon, Jun 20, 2016 at 2:56 PM, khali singh <khali3620@xxxxxxxxx> wrote: >> I wonder if anyone has some numbers on the RAM consumption of a >> supplicant. I know it would be depend on the actual EAP method used, >> but I was wondering what kind of numbers are we talking about. Is it a >> few kB or way more? >> >> I was thinking to build a stripped down version of wpa_supplicant with >> only the bare essentials and one EAP method for usage in IoT type >> devices. > I did this recently, for a basic open connection, using mac80211_hwsim > i got the total heap consumption to be about 130KB. (using massif from > valgrind). > > n time(i) total(B) useful-heap(B) extra-heap(B) stacks(B) > > ------------------------------------------------------------------------------------------------- > > 50 7,734,291 130,008 90,039 39,969 0 > > 51 7,814,496 59,928 47,991 11,937 0 > > 52 7,898,388 12,640 12,047 593 0 _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
