[lkml]   [2010]   [May]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Unexpected splice "always copy" behavior observed

On Thu, 20 May 2010, Nick Piggin wrote:
> Well I mean a full invalidate -- invalidate_mapping_pages -- so there is
> literally no pagecache there at all.

Umm. That won't work. Think mapped pages. You can't handle them
atomically, so somebody will page-fault them in.

So you'd have to have a "invalidate_and_replace()" to do it atomically
while holding the mapping spinlock or something.

And WHAT IS THE POINT? That will be about a million times slower than
just doing the effing copy in the first place!

Memory copies are _not_ slow. Not compared to taking locks and doing TLB


 \ /
  Last update: 2010-05-19 17:37    [W:0.077 / U:4.432 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site