From: jamal <hadi@cyberus.ca>
To: Patrick McHardy <kaber@trash.net>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH][XFRM] export SPD info
Date: Fri, 27 Apr 2007 10:29:28 -0400 [thread overview]
Message-ID: <1177684168.4059.38.camel@localhost> (raw)
In-Reply-To: <463200CC.6010207@trash.net>
On Fri, 2007-27-04 at 15:55 +0200, Patrick McHardy wrote:
>
> It it really worth the extra code for dumping them conditionally?
> The attributes are neither large nor will they be sent very often.
>
That thought did cross my mind when i was coding this;-> I hate the way
netlink filters are done in user space with iproute2 - dumping 50
objects just so i can get to one. So i used that as my guiding
principle; i have no qualms with the few extra lines.
Actually, I was hoping it would provide motivation for someone else to
do a better filtering scheme (which sits in the kernel).
cheers,
jamal
next prev parent reply other threads:[~2007-04-27 14:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 13:43 [PATCH][XFRM] export SPD info jamal
2007-04-27 13:55 ` Patrick McHardy
2007-04-27 14:29 ` jamal [this message]
2007-04-29 4:19 ` David Miller
2007-04-30 12:04 ` jamal
2007-04-29 4:21 ` David Miller
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=1177684168.4059.38.camel@localhost \
--to=hadi@cyberus.ca \
--cc=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
/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.