netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: hadi@cyberus.ca
Cc: "David S. Miller" <davem@davemloft.net>,
	Maillist netdev <netdev@oss.sgi.com>
Subject: Re: [NET]: Avoid useless iterating in netlink dump functions
Date: Fri, 06 May 2005 23:12:52 +0200	[thread overview]
Message-ID: <427BDDD4.1000808@trash.net> (raw)
In-Reply-To: <1115413473.13922.38.camel@localhost.localdomain>

jamal wrote:
> Looks good - you may also wanna treat tcf_dump_walker() and
> xfrm_dump_sa() the same way then. 
> 

action dumping is on my list for more treatment than this :)
xfrm_dump_sa()/xfrm_state_walk() could be changed to skip
smarter, but that is a different kind of change.

Regards
Patrick

  reply	other threads:[~2005-05-06 21:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-06 15:39 [NET]: Avoid useless iterating in netlink dump functions Patrick McHardy
2005-05-06 21:04 ` jamal
2005-05-06 21:12   ` Patrick McHardy [this message]
2005-05-06 21:17     ` jamal
2005-05-06 21:27       ` Patrick McHardy
2005-05-07 12:10         ` jamal

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=427BDDD4.1000808@trash.net \
    --to=kaber@trash.net \
    --cc=davem@davemloft.net \
    --cc=hadi@cyberus.ca \
    --cc=netdev@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).