Nikolay Borisov <kernel@xxxxxxxx> writes:
>> diff --git a/fs/namespace.c b/fs/namespace.c
>> index 2b8aa15fd6df..2ce987af9afa 100644
>> --- a/fs/namespace.c
>> +++ b/fs/namespace.c
>> @@ -31,6 +31,8 @@ static unsigned int m_hash_mask __read_mostly;
>> static unsigned int m_hash_shift __read_mostly;
>> static unsigned int mp_hash_mask __read_mostly;
>> static unsigned int mp_hash_shift __read_mostly;
>> +static unsigned int mr_hash_mask __read_mostly;
>> +static unsigned int mr_hash_shift __read_mostly;
>>
>> static __initdata unsigned long mhash_entries;
>> static int __init set_mhash_entries(char *str)
>> @@ -52,6 +54,16 @@ static int __init set_mphash_entries(char *str)
>> }
>> __setup("mphash_entries=", set_mphash_entries);
>>
>> +static __initdata unsigned long mrhash_entries;
>> +static int __init set_mrhash_entries(char *str)
>> +{
>> + if (!str)
>> + return 0;
>> + mrhash_entries = simple_strtoul(str, &str, 0);
>
> Nit: Any particular reason for using simple_* rather than kstrto* family
> of functions?
That is what set_mhash_entries, and set_mphash_entries do, and I
maintained the existing style in the code.
It does look like a followup change to add error handling in the
pathological cases might be worthwhile.
Although it would probably be even better to convert these hash tables
into rcu resizeable hash tables that can automatically grow to the size
needed.
Eric
--
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
