[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <863e9df20805220007r36089c93p6f2a787818aa150c@mail.gmail.com>
Date: Thu, 22 May 2008 12:37:20 +0530
From: "Abhishek Sagar" <sagar.abhishek@...il.com>
To: "Srinivasa D S" <srinivasa@...ibm.com>,
"Jim Keniston" <jkenisto@...ibm.com>
Cc: linux-kernel@...r.kernel.org,
"Andrew Morton" <akpm@...ux-foundation.org>,
"Ananth Mavinakayanahalli" <ananth@...ibm.com>,
"Masami Hiramatsu" <mhiramat@...hat.com>,
"Srikar Dronamraju" <srikar@...ux.vnet.ibm.com>
Subject: Re: [RFC] [PATCH] To improve kretprobe scalability
On 5/21/08, Srinivasa D S <srinivasa@...ibm.com> wrote:
> Solution:
> 1) Instead of having one global lock to protect kretprobe instances
> present in kretprobe object and kretprobe hash table. We will have two locks,
> one lock for protecting kretprobe hash table and another lock for kretporbe
> object.
Is it possible to get rid of the kretprobe hash table itself and lose
the kretprobe_lock? It seems like it is just doing a pid-to-instance
mapping. These return instances could be queued in the "current"
task_struct in a LIFO manner. Mutation to this per-task list can be
done with local irqs off...
--
Regards,
Abhishek Sagar
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists