All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: David Miller <davem@davemloft.net>
Cc: cratiu@ixiacom.com, netdev@vger.kernel.org,
	ixlk-cr@farscape.ixiacom.com, pchakrabarti@ixiacom.com
Subject: Re: [RFC PATCH] extend RTM_GETNEIGH to allow getting more precise information
Date: Mon, 25 Jan 2010 14:51:54 +0100	[thread overview]
Message-ID: <4B5DA1FA.4030905@trash.net> (raw)
In-Reply-To: <20100123.021233.122638456.davem@davemloft.net>

David Miller wrote:
> From: Cosmin Ratiu <cratiu@ixiacom.com>
> Date: Fri, 15 Jan 2010 18:42:59 +0200
> 
>> Please have a look at this patch which tries to solve a problem we 
>> encountered.
>>
>> The background is that RTM_GETNEIGH netlink message is used to get a complete 
>> dump of a neighbor table. Sometimes, that's too much (especially when you have 
>> a lot of neighbors). This patch allows one to specify the IPv4/6 address of a 
>> neighbor and the device index through which it is accessible in order to 
>> obtain only that entry.
>>
>> If you have other suggestions on how to accomplish this task, please let us 
>> know.
> 
> Please add a netlink attribute to specify lookup keys.
> 
> Adding specifiers to the end of the existing request message
> error prone and creates trouble in the future if someone gets
> the idea to add something more.

It should also use a seperate callback for looking up individual
entries instead of the NLM_F_DUMP callback.

      reply	other threads:[~2010-01-25 13:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-15 16:42 [RFC PATCH] extend RTM_GETNEIGH to allow getting more precise information Cosmin Ratiu
2010-01-23 10:12 ` David Miller
2010-01-25 13:51   ` Patrick McHardy [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B5DA1FA.4030905@trash.net \
    --to=kaber@trash.net \
    --cc=cratiu@ixiacom.com \
    --cc=davem@davemloft.net \
    --cc=ixlk-cr@farscape.ixiacom.com \
    --cc=netdev@vger.kernel.org \
    --cc=pchakrabarti@ixiacom.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.