[lkml]   [2006]   [Aug]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [Devel] Re: [PATCH] kthread: saa7134-tvaudio.c
Cedric Le Goater wrote:
> Eric W. Biederman wrote:
> [ ... ]
>>>>That plus the obvious bit. For the pid namespace we have to declare
>>>>war on people storing a pid_t values. Either converting them to
>>>>struct pid * or removing them entirely. Doing the kernel_thread to
>>>>kthread conversion removes them entirely.
>>>we've started that war, won a few battles but some drivers need more work
>>>that a simple replace. If we could give some priorities, it would help to
>>>focus on the most important ones. check out the list bellow.
>>Sure, I think I can help.
>>There are a couple of test I can think of that should help.
>>1) Is the pid value stored. If not a pid namespace won't affect
>> it's normal operation.
> I've extracted this list from a table which includes a pid cache column.
> this pid cache column is not complete yet. I'd be nice if we could use a
> wiki to maintain this table, the existing openvz or vserver wiki ?
feel free to use
we will create a 'Developement' category then for such pages.
I think we can help with the patches soon as well.

>>I do agree from what I have seen, that changing idioms to the kthread way of
>>doing things isn't simply a matter of substitute and replace which is
>>unfortunate. Although the biggest hurdle seems to be to teach kernel threads
>>to communicate with something besides signals. Which is a general help anyway.
>>Unfortunately I'm distracted at the moment so I haven't gone through the entire
>>list but I hope this helps.
If we have some list on the wiki, people could assign the issues to themself and
prepare the patches. Thus work could be paralleled a bit.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-08-30 18:35    [W:0.097 / U:0.128 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site