Actually, I am plugging in my own data blocks into the skbuff->data
pointer from the drivers themselves. When the driver allocates an
skbuff, I use an alternate cache allocator to load the buffer
into the skbuff, and I leave the two attached. skb_release_data does
not release one of my data blocks. These blocks are 4K aligned so
I am not in the middle of a cache line (I think) in the data portion
when DMA is initiated.
> ring may simply be hiding the fact that the recycled skbuff has dirty
> cached data that has to be written back. Does the combination of hardware
This is probably happening. I have an Arium here now, and am hooking
it up. I can get memory bus traces and provide what's actually
happening on the bus. I do not ever DMA into a partial cache line.
Jeff
> you have do the right thing when it comes to the invalidating - and do
> you ever DMA into a partial cache line ?
>
> Alan
-
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/