X-Spam-Check-By: sourceware.org Date: Thu, 3 Aug 2006 19:08:05 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: cygwin copy problems usb 2.0 Message-ID: <20060803170805.GC8152@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <080320060154 DOT 8210 DOT 44D157570002EFAE0000201222064244130A050E040D0C079D0A AT comcast DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <080320060154.8210.44D157570002EFAE0000201222064244130A050E040D0C079D0A@comcast.net> User-Agent: Mutt/1.4.2i Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Aug 3 01:54, Eric Blake wrote: > > >I'm really seeing the non-optimized cygwin cp behaviour causing bad > > >reputation, which could be easily patched and maybe even accepted > > >upstream. Who knows. Eric what do think? Would it be worthful to think > > >about? > > I don't really want to maintain a Windows API patch, and doubt that Good. > it would be accepted upstream. Now if there were something more > POSIX-y that we could do to speed things up, such as posix_fadvise, posix_fadvise can't be implemented nicely, AFAICS. The POSIX semantics require an already opened file and the advice is given for an offset and a length. The Windows semantics only allow to give the advice for the whole file, and only switching between FILE_SEQUENTIAL_ONLY or "normal", using ZwSetInformationFile. By re-opening the file using ZwOpenFile it would also be possible to toggle the FILE_RANDOM_ACCESS flag. Still, it's always for the whole file, not for an area giving offset and length. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/