[Top] [All Lists]

Re: [RFC] Yield in netlink_broadcast when congested

To: tgraf@xxxxxxx (Thomas Graf)
Subject: Re: [RFC] Yield in netlink_broadcast when congested
From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
Date: Mon, 18 Oct 2004 07:31:14 +1000
Cc: herbert@xxxxxxxxxxxxxxxxxxx, pablo@xxxxxxxxxxx, hadi@xxxxxxxxxx, davem@xxxxxxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <20041017130838.GW21977@xxxxxxxxxxxxxx>
Organization: Core
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: tin/1.7.4-20040225 ("Benbecula") (UNIX) (Linux/2.4.27-hx-1-686-smp (i686))
Thomas Graf <tgraf@xxxxxxx> wrote:
> locking implemented in any application as far as i know, f.e. iproute2
> looks up an ifindex and uses it w/o locking so the link could
> be renamed or removed in between. If we ever implement the ietf

IMHO that particular case should be dealt with by providing a way for
the application to bind to a device and thus holding a reference on it.
This reference should then ensure that the interface name/ifindex doesn't
go away until the appliation relinquinshes it or dies (i.e., the socket
where the binding resides is closed).

> in userspace. This daemon could easly lead to multiple listeners
> in a single process. Nevertheless, I guess we can ignore it for now as

Multiple listeners in a single process should be fine as long as they're
listening to different groups.  It's only when you listen to the same
thing multiple times that you're going to overrun your time-slice and
then your receive queue.

Visit Openswan at
Email: Herbert Xu ~{PmV>HI~} <herbert@xxxxxxxxxxxxxxxxxxx>
Home Page:
PGP Key:

<Prev in Thread] Current Thread [Next in Thread>