From owner-freebsd-hackers@FreeBSD.ORG Sat Apr 7 23:01:43 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 328A9106566C for ; Sat, 7 Apr 2012 23:01:43 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id EAA158FC08 for ; Sat, 7 Apr 2012 23:01:42 +0000 (UTC) Received: by obbwc18 with SMTP id wc18so5890209obb.13 for ; Sat, 07 Apr 2012 16:01:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=L+/exG3J+loeMSU4Dn3IHePTLcDcDJ4zkW4wO7/HpmA=; b=ubWZBcuiEp584jNg33s5PBzi9KQCrRMH7EREtOUsS2TtmBeXcIq2E4CWN5tJVEfqHm nTCJYu7oJedWIO86KPGTjdgIf0uLah53IRuxRzLogBSu5XkCBEM2TzUc71ysdtz3FgWq wPkfp5ZWuEFN5c5lpRxtaYZXjPvbFFNn7Op7WA5SvHl3tLa17aVcWCsPNIXDjIMB7mOb oxWQXKJji/NVUOPlR69GfioexuVFMypM040z1YW/GR9EonMo/Fs5+XRDgJTxEytctrWG 2iwI/tCCfLIit5C2H3doionvzDjT2Rw5xVoaSlSrACuSgFJP5MTX5GPOQ+PIhSKMbeRh Lm/w== Received: by 10.60.18.198 with SMTP id y6mr3636104oed.38.1333839702505; Sat, 07 Apr 2012 16:01:42 -0700 (PDT) MIME-Version: 1.0 Sender: ivoras@gmail.com Received: by 10.182.85.71 with HTTP; Sat, 7 Apr 2012 16:01:01 -0700 (PDT) In-Reply-To: <0D2E65B3D0AB4A6483C26A613FC73F83@dudu.ro> References: <0D2E65B3D0AB4A6483C26A613FC73F83@dudu.ro> From: Ivan Voras Date: Sun, 8 Apr 2012 01:01:01 +0200 X-Google-Sender-Auth: kqudcxh1SRU9JlXTE2BJwmMM91s Message-ID: To: Vlad Galu Content-Type: text/plain; charset=UTF-8 Cc: freebsd-hackers Subject: Re: Socket buffer usage X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Apr 2012 23:01:43 -0000 On 7 April 2012 23:36, Vlad Galu wrote: > This might not exactly be what you want, but struct kevent has a member called "data" which, for sockets and pipes, returns the number of available bytes to read (or write) for EVFILT_READ (or EVFILT_WRITE) events. > That's a good idea but I'm actually trying to find out why my write events are not firing, so I can't get to that information.