On Tue, Oct 23, 2007 at 10:19:06PM -0400, Eric St-Laurent wrote:CoW isn't in the slightest bit helpful. The point of these is to provide an accumulator, therefore the majority of accesses to these stringbufs are writes. If we were trying to get rid of char * throughout the kernel, that might make some sense; stringbufs have a more limited target though. I think you missed the part of the patch where I said that the stringbuf is normally allocated on the stack or as part of some other structure. The only thing that should be allocated is the string itself. -- Intel are signing my paycheques ... these opinions are still mine "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step." -
| H. Peter Anvin | Re: [RFC 00/15] x86_64: Optimize percpu accesses |
| Greg Kroah-Hartman | [PATCH 008/196] Chinese: add translation of volatile-considered-harmful.txt |
| Greg KH | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Alex Chiang | [PATCH 1/4] Remove path attribute from sgi_hotplug |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | Re: [GIT]: Networking |
| Eric Dumazet | Re: [PATCH 3/3] Convert the UDP hash lock to RCU |
