On Fri, Feb 15 2013, Glauber Costa wrote:
>>> +struct mem_cgroup;
>>> +#ifdef CONFIG_MEMCG_KMEM
>>> +/*
>>> + * We will reuse the last bit of the pointer to tell the lru subsystem that
>>> + * this particular lru should be replicated when a memcg comes in.
>>> + */
>>
>> From this patch it seems like 0x1 is a magic value rather than bit 0
>> being special. memcg_lrus is either 0x1 or a pointer to an array of
>> struct list_lru_array. The array is indexed by memcg_kmem_id.
>>
>
> Well, I thought in terms of "set the last bit". To be honest, when I
> first designed this, I figured it could possibly be useful to keep the
> bit set at all times, and that is why I used the LSB. Since I turned out
> not using it, maybe we could actually resort to a fully fledged magical
> to avoid the confusion?
To avoid confusion, I'd prefer a magic value. This allows callers to
not worrying about having to strip off the low order bit, if it's later
always set for some reason. But I'm not even sure we need a magic value
or magic bit (see below).
>>> +static inline void lru_memcg_enable(struct list_lru *lru)
>>> +/*
>>> + * This will return true if we have already allocated and assignment a memcg
>>> + * pointer set to the LRU. Therefore, we need to mask the first bit out
>>> + */
>>> +static inline bool lru_memcg_is_assigned(struct list_lru *lru)
>>> +{
>>> + return (unsigned long)lru->memcg_lrus & ~0x1ULL;
>>
>> Is this equivalent to?
>> return lru->memcg_lrus != NULL && lru->memcg_lrus != 0x1
>>
> yes. What I've explained above should help clarifying why I wrote it
> this way. But if we use an actual magical (0x1 is a bad magical, IMHO),
> the intentions become a lot clearer.
Does the following work and yield simpler code?
1. add a 'bool memcg_enabled' parameter to list_lru_init()
2. rename all_lrus to all_memcg_lrus
3. only add lru to all_memcg_lrus if memcg_enabled is set
4. delete lru_memcg_enable()
5. redefine lru_memcg_is_assigned() to just test (lru->memcg_lrus == NULL)
Then we don't need a magic valid (or LSB) to identify memcg enabled
lrus. Any lru in the all_memcg_lrus list is memcg enabled.
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
