From: Patrick McHardy <kaber@trash.net>
To: hadi@cyberus.ca
Cc: "Herbert Xu" <herbert@gondor.apana.org.au>,
"David Miller" <davem@davemloft.net>,
"Timo Teräs" <timo.teras@iki.fi>,
netdev@vger.kernel.org
Subject: Re: [RFC]: xfrm by mark
Date: Mon, 08 Feb 2010 16:35:25 +0100 [thread overview]
Message-ID: <4B702F3D.3080104@trash.net> (raw)
In-Reply-To: <1265642914.3688.71.camel@bigi>
jamal wrote:
> On Mon, 2010-02-08 at 16:00 +0100, Patrick McHardy wrote:
>
>> I'd prefer masks since the mark size is pretty small and its already
>> quite complicated to fit everything in 32 bit in complex setups.
>> We also support masks everywhere else (I believe) for mark values
>> nowadays.
>
> I could still use the mask also as it is consistently
> being used today i.e (mark & x->mask) == x->mark
> the only challenge i can think of is operational. How
> do you see me activating the use of these marks? The setups
> i see:
>
> -By default if i use pfkey or old iproute2 i can have both
> mask and val as 0. no problem there..
> -If i was to insert table entries with say mark val 4 and mask
> of 0, that would continue to work since mark is ignored.
> -if at some later point i want to use this mark 4, do i just change
> the mask? That may not scale well if you have a gazillion entries.
> If i used a sysctl all i would do is just turn on the
> syctl and the check becomes:
> syctl_use_mark && ((mark & x->mask) == x->mark)
Why would you want to insert entries with a mark and not use
them immediately? We don't support this anywhere without
replacing entries.
next prev parent reply other threads:[~2010-02-08 15:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-07 18:32 [RFC]: xfrm by mark jamal
2010-02-08 13:30 ` Patrick McHardy
2010-02-08 14:58 ` jamal
2010-02-08 15:00 ` Patrick McHardy
2010-02-08 15:28 ` jamal
2010-02-08 15:35 ` Patrick McHardy [this message]
2010-02-08 15:56 ` 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=4B702F3D.3080104@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=hadi@cyberus.ca \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=timo.teras@iki.fi \
/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.