lkml.org 
[lkml]   [2003]   [Feb]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC] Migrating net/sched to new module interface
Hi,

On Fri, 14 Feb 2003, Rusty Russell wrote:

> > It's not the same, please see:
> > http://marc.theaimsgroup.com/?l=linux-kernel&m=104284223130775&w=2
> > I explained why the current module locking is more complex and why it's
> > actually a three stage delete.
>
> No, here is where you show *your* ignorance of kernel locking idioms,
> and that your axiom is that "the new system is more complex".

Well, it should be simple then to point out the problem, would you
_please_ do it?

> > Rusty, above are real problems, the module locking fixes these problems
> > during module_init/module_exit, but how can these problems fixed in the
> > other cases and how does the module locking help?
>
> This isn't even a sensible question: "This is not a module problem.
> How does module locking help?"
>
> You're wasting your own valuable time, too.

I hoped we could discuss locking problems, as I said these problems are
real, so it should be worth to describe possible solutions. Then we can
compare the different locking mechanism and maybe we find one, which not
only solves a part of the problem.

Rusty, I'm asking all these questions on purpose, I want to help you to
understand the complete problem and how limited your solutions are. So
either please answer my questions or point out the mistakes in my
argumentation.

bye, Roman

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:33    [W:0.199 / U:0.096 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site