Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752818Ab3CCDQf (ORCPT ); Sat, 2 Mar 2013 22:16:35 -0500 Received: from mail-bk0-f49.google.com ([209.85.214.49]:49945 "EHLO mail-bk0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752671Ab3CCDQe (ORCPT ); Sat, 2 Mar 2013 22:16:34 -0500 MIME-Version: 1.0 In-Reply-To: <1362280145.15793.70.camel@edumazet-glaptop> References: <1361820175.6781.13.camel@edumazet-glaptop> <1362280145.15793.70.camel@edumazet-glaptop> From: Ulrich Drepper Date: Sat, 2 Mar 2013 22:16:12 -0500 Message-ID: Subject: Re: sendfile and EAGAIN To: Eric Dumazet Cc: Linux Kernel Mailing List , Al Viro Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 774 Lines: 17 On Sat, Mar 2, 2013 at 10:09 PM, Eric Dumazet wrote: > > Using non blocking IO means the sender (and the receiver) must be able > to perform several operations, as long as the whole transfert is not > finished. Certainly, and this is implemented. But the receiver never gets the rest of the data while the sender (most of the time) gets notified that everything is sent. I don't have a reduced test case yet. Hopefully I'll get to it sometime soon. For now I worked around it by not using sendfile. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/