Messages in this thread | | | Date | Fri, 6 Aug 1999 15:14:06 -0700 | From | "David S. Miller" <> | Subject | Re: No kmem_cache_destroy? |
| |
Date: Fri, 6 Aug 1999 19:00:23 +0100 From: Steve Dodd <dirk@lamia.loth.demon.co.uk>
I did this a while back. The required changes to NFS become one liners. Attached (all but the NFS changes).
Personally I don't think that adding a lookup method is the way to go. Simply because it does require changes at the call sites.
If you add the logic to kmem_cache_create itself, you require no changes, you just return the found kmem_cache_t instead of creating a new one. I think this is much simpler.
I do totally agree with the strdup changes, I never realized that, how silly to have multiple implementations. :-)
Later, David S. Miller davem@redhat.com
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |