X-Spam-Check-By:	sourceware.org
From:	ericblake AT comcast DOT net (Eric Blake)
To:	cygwin AT cygwin DOT com
Subject:	Re: cygwin copy problems usb 2.0
Date:	Thu, 03 Aug 2006 19:08:08 +0000
Message-Id:	<080320061908.15481.44D24998000AE51600003C7922064244130A050E040D0C079D0A@comcast.net>
X-Mailer:	AT&T Message Center Version 1 (Apr 11 2006)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

> 
> Theoretically, it's possible to implement posix_fadvise only for offset=0
> and length=<length-of-file>, and have it fail with EINVAL otherwise...
> While technically not POSIX-compliant, it would still allow for better
> implementation of things like copy...

Even better, have it return 0 for success but do nothing when offset!=0
or len!= 0.  It's called posix_fadvise for a reason - the implementation is
free to ignore the advice when it can't reasonably use it.  EINVAL should
only be used when passing a bad argument (ie. outside the range of
defined POSIX_FADV_* constants).

There is also posix_fallocate, which may help the case of cp.

-- 
Eric Blake

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -