Re: [Lse-tech] Re: [RFC][PATCH] Scalable FD Management using Read-Copy-Update

• Next message: Valdis.Kletnieks@vt.edu: "Re: scheduler went mad?"
• Previous message: Andrew Morton: "Re: [PATCH] 4th try: i386 rw_semaphores fix"
• In reply to: Maneesh Soni: "Re: [Lse-tech] Re: [RFC][PATCH] Scalable FD Management using Read-Copy-Update"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

From: "Maneesh Soni" <smaneesh@in.ibm.com>
...
> Though I intend to do some
> profiling to look into this but it will be helpfull if you can tell me
if there
> is some known thing regarding this.
...

Another useful tool is Lockmeter, which gives you visibility to what's
happening with spinlock_t and rwlock_t usage.
http://oss.sgi.com/projects/lockmeter

John Hawkes
hawkes@engr.sgi.com

-
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/

• Next message: Valdis.Kletnieks@vt.edu: "Re: scheduler went mad?"
• Previous message: Andrew Morton: "Re: [PATCH] 4th try: i386 rw_semaphores fix"
• In reply to: Maneesh Soni: "Re: [Lse-tech] Re: [RFC][PATCH] Scalable FD Management using Read-Copy-Update"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sun Apr 15 2001 - 21:00:19 EST