Messages in this thread | | | Date | Wed, 10 Nov 1999 01:45:22 +0100 (MET) | From | Gerard Roudier <> | Subject | Re: PATCH 2.3.26: kmalloc GFP_ZEROt |
| |
On Tue, 9 Nov 1999, Alan Cox wrote:
> > course as you won't pay the cost anymore. That's a different scenario. The > > only problem is that I am not aware of any zeroing hardare DMA controller > > on my machines. > > NCR53c8xx... ?
Indeed they may be used so, but it is the actual memory that will be zeroed with the cache invalidating or snooping the accesses. May-be having some pool of zeroed memory or zeroing some memory is useful for security issue, but speaking of pooled or cached objects, we probably want to most of the time reuse constructed instances that have been stated free and only zero parts that need to be so. The bzero-mania does not look fine programming to me.
Btw, I probably missed most of the the discussion since I didn't follow it. :-)
Gérard.
PS: If we want to be able to write zero-filled blocks to a disk without bzero overhead, for example, we can reserve a small amount of physical pages filled with zeros at startup.
- 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/
| |