X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 	tests=AWL,BAYES_00
X-Spam-Check-By: sourceware.org
Date: Wed, 1 Jul 2009 09:40:33 -0500
From: Brian Ford <Brian.Ford@FlightSafety.com>
Reply-To: cygwin@cygwin.com
To: cygwin@cygwin.com
Subject: Re: Call for TESTING (was Re: [1.7.0-50] scp progress counter  flies   through first 175 MB or so)
In-Reply-To: <20090701092617.GU30864@calimero.vinschen.de>
Message-ID: <Pine.CYG.4.58.0907010935130.4092@PC1163-8460-XP.flightsafety.com>
References: <20090625145005.GB18338@ednor.casa.cgf.cx>  <20090628193155.GA10407@ednor.casa.cgf.cx> <20090629092857.GZ30864@calimero.vinschen.de>  <20090629095322.GD30864@calimero.vinschen.de> <20090629142348.GB19123@ednor.casa.cgf.cx>  <20090629144030.GC19123@ednor.casa.cgf.cx> <4A490F0E.6040806@etr-usa.com>  <20090630112617.GS30864@calimero.vinschen.de> <4A4A3B64.4030004@etr-usa.com>  <Pine.CYG.4.58.0906301407590.4092@PC1163-8460-XP.flightsafety.com>  <20090701092617.GU30864@calimero.vinschen.de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On Wed, 1 Jul 2009, Corinna Vinschen wrote:

> On Jun 30 14:23, Brian Ford wrote:
> > Even more so for context switches ;-):
> >
> > http://www.cygwin.com/ml/cygwin-developers/2007-10/msg00040.html
> >
> > although this performance penalty was removed from read/write and friends:
> >
> > http://www.cygwin.com/ml/cygwin-developers/2007-12/msg00004.html
> >
> > it is still present for send/recv and friends.
>
> I removed the sig_dispatch_pending calls from send/recv and friends.

Thank you!  This should have removed the thread handshake overhead from
most all I/O calls now.  I just wish we could figure out a way to avoid
it everywhere unless it is actually necessary.  I know, PTC :-).

> Note, however, that this has no influence on the ssh/scp results we were
> talking about in this thread.  ssh/scp are using read/write calls.

Sorry, I should have investigated and bench marked the difference.

-- 
Brian Ford
Staff Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
the best safety device in any aircraft is a well-trained crew...

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

