Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753164AbZILJlL (ORCPT ); Sat, 12 Sep 2009 05:41:11 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752843AbZILJlK (ORCPT ); Sat, 12 Sep 2009 05:41:10 -0400 Received: from tservice.net.ru ([195.178.208.66]:35637 "EHLO tservice.net.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752318AbZILJlJ (ORCPT ); Sat, 12 Sep 2009 05:41:09 -0400 Date: Sat, 12 Sep 2009 13:41:10 +0400 From: Evgeniy Polyakov To: Eric Paris Cc: Jamie Lokier , David Miller , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, netdev@vger.kernel.org, viro@zeniv.linux.org.uk, alan@linux.intel.com, hch@infradead.org Subject: Re: [PATCH 1/8] networking/fanotify: declare fanotify socket numbers Message-ID: <20090912094110.GB24709@ioremap.net> References: <20090911052558.32359.18075.stgit@paris.rdu.redhat.com> <20090911.114620.260824240.davem@davemloft.net> <1252697613.2305.38.camel@dhcp231-106.rdu.redhat.com> <20090911204602.GA19371@shareable.org> <1252703626.2305.50.camel@dhcp231-106.rdu.redhat.com> <20090911212731.GA19901@shareable.org> <1252705902.2305.83.camel@dhcp231-106.rdu.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1252705902.2305.83.camel@dhcp231-106.rdu.redhat.com> User-Agent: Mutt/1.5.13 (2006-08-11) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1068 Lines: 23 On Fri, Sep 11, 2009 at 05:51:42PM -0400, Eric Paris (eparis@redhat.com) wrote: > For some things yes, some things no. I'd have to understand where loss > can happen to know if it's feasible. If I know loss happens in the > sender context that's great. If it's somewhere in the middle and the > sender doesn't immediately know it'll never be delivered, yes, I don't > think it can solve all my needs. How many places can and skb get lost > between the sender and the receiver? When queue is full or you do not have enough RAM. Both are reported at 'sending' time. As of your description of netlink/socket usage - you will have to peek skb queue, which is rather error-prone operation. Also you will have to implement own skb destructor to mess with private reference counters and netlink bits. -- Evgeniy Polyakov -- 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/