[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090911204602.GA19371@shareable.org>
Date: Fri, 11 Sep 2009 21:46:02 +0100
From: Jamie Lokier <jamie@...reable.org>
To: Eric Paris <eparis@...hat.com>
Cc: David Miller <davem@...emloft.net>, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org, netdev@...r.kernel.org,
viro@...iv.linux.org.uk, alan@...ux.intel.com, hch@...radead.org
Subject: Re: [PATCH 1/8] networking/fanotify: declare fanotify socket numbers
Eric Paris wrote:
> > I would really prefer if you worked on eliminating the problem that
> > prevents you from using netlink instead.
>
> I'm not really sure if I can, although I'd love to hear input from
> someone who knows the netlink code on how I can make it do what I need.
> I'm really not duplicating much other than the NLMSG_OK and NLMSG_NEXT
> macros. My code doesn't even use skbs and I'm not savy enough to really
> know how I could. I'm more than willing to work on it if someone can
> point me to how it might work.
Let's turn the question around.
Since you're doing lots of non-sockety things, and can't tolerate
dropped packets - why isn't it a character device? What's the reason
for using a socket at all?
(I'm reminded of /dev/poll, /dev/epoll and /dev/inotify :-)
-- Jamie
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists