[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <A2BAEFC30C8FD34388F02C9B3121859D1C2C9AB0@eusaamb103.ericsson.se>
Date: Mon, 15 Sep 2014 16:35:34 +0000
From: Jon Maloy <jon.maloy@...csson.com>
To: David Miller <davem@...emloft.net>,
Richard Alpe <richard.alpe@...csson.com>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"tipc-discussion@...ts.sourceforge.net"
<tipc-discussion@...ts.sourceforge.net>
Subject: RE: [PATCH net-next 04/14] tipc: add sock dump to new netlink api
> -----Original Message-----
> From: netdev-owner@...r.kernel.org [mailto:netdev-
> owner@...r.kernel.org] On Behalf Of David Miller
> Sent: September-15-14 11:39 AM
> To: Richard Alpe
> Cc: netdev@...r.kernel.org; tipc-discussion@...ts.sourceforge.net
> Subject: Re: [PATCH net-next 04/14] tipc: add sock dump to new netlink api
>
> From: Richard Alpe <richard.alpe@...csson.com>
> Date: Mon, 15 Sep 2014 09:55:24 +0200
>
> > The amount of publications a socket can have is large (~65 000). Do
> > you still think this a viable solution?
>
> Then maybe you want to have a completely separate netlink operation to
> dump the publications, the request would provide a key saying which
> socket's publications to dump.
A compromise could be to list a fix maximum number (100?) of publications
that cover all "normal" cases, and return a hint indicating that there is
more if this was not enough. For 99% of the sockets this would be enough,
and for the remaining ones the tool would have to use the second operation
to make the listing complete.
///jon
> --
> 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
--
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