Search Linux Wireless

Re: [RFC] design discussion: Collecting information for (non-peer) stations

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Feb 18, 2013 at 07:43:26 -0800, Johannes Berg wrote:
> > I did not like this approach because the sta_info struct is so big that
> > when we want to fill the stats substruct only we will waste a lot of bytes.
> 
> I don't understand your point.
> 
> struct sta_info {
>    ...
>    struct stats stats;
> };

My concern is about those "..." that we are allocating within the sta_info struct
that we will never use for every non-peer station.

While if we used the struct below (with its own hash table), we would allocate
only the space needed for the stats.

> 
> struct stats_entry {
>    struct hash/list/whatever;
>    struct stats stats;
> };
> 


no?
Maybe I misunderstood your idea?

Cheers,


-- 
Antonio Quartulli

..each of us alone is worth nothing..
Ernesto "Che" Guevara

Attachment: pgp3XVKFlpIiD.pgp
Description: PGP signature


[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Wireless Personal Area Network]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite Hiking]     [MIPS Linux]     [ARM Linux]     [Linux RAID]

  Powered by Linux