From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anna Schumaker Subject: Re: [PATCH v1 0/8] VFS: In-kernel copy system call Date: Tue, 8 Sep 2015 11:08:03 -0400 Message-ID: <55EEF9D3.6050505@Netapp.com> References: <1441397823-1203-1-git-send-email-Anna.Schumaker@Netapp.com> <4B41043F-5D85-42D6-8F20-2DCC45930EF4@dilger.ca> <20150905083342.GG22011@ZenIV.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Cc: , , , , , , , , , To: Al Viro , Andreas Dilger Return-path: In-Reply-To: <20150905083342.GG22011-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org> Sender: linux-api-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-fsdevel.vger.kernel.org On 09/05/2015 04:33 AM, Al Viro wrote: > On Fri, Sep 04, 2015 at 04:25:27PM -0600, Andreas Dilger wrote: > >> This is a bit of a surprising result, since in my testing in the >> past, copy_{to/from}_user() is a major consumer of CPU time (50% >> of a CPU core at 1GB/s). What backing filesystem did you test on? > > While we are at it, was cp(1) using read(2)/write(2) loop or was it using > something else (sendfile(2), for example)? cp uses a read / write loop, and has some heuristics for guessing an optimum buffer size. Anna >