>> 2. Keep the current comm[16] as-is and introduce a separate pointer >> to store kthread's long name > > I'm OK with this. Hopefully more would chime in too. What you propose sounds sane to me. -- Thanks, David / dhildenb
>> 2. Keep the current comm[16] as-is and introduce a separate pointer >> to store kthread's long name > > I'm OK with this. Hopefully more would chime in too. What you propose sounds sane to me. -- Thanks, David / dhildenb