This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [Patch 2/5][Djprobe]Djprobe Coexist with Kprobes


On Thu, Oct 13, 2005 at 07:12:09PM +0900, Masami Hiramatsu wrote:
> Hi, Anil
> 
> 
> 
> >
> > Also, I see the same linear search happening inside work_check_djprobe_instance().
> > As I understand you are scheduling this function on all the cpus and inside this
> > function you are doing a linear search for djprobe instances that too holding
> > a spin lock and thus making other thread executing this function on different
> cpus to
> > wait untill you finish serial search on this cpu. Hence my suggestion to look into
> > optimizing this search.
> 
> OK, that is a problem. I have an idea of "per-probe work"s to solve it.
> This will allocate a lot of works and insert it into the workqueues on each cpu.
> Is this acceptable?

How about calling flush_scheduled_work(). Will this work? 

Cheers,
Anil


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]