From: "Javier Cardona" <javier@cozybit.com>
To: "Stephen Hemminger" <shemminger@linux-foundation.org>
Cc: "Dan Williams" <dcbw@redhat.com>,
"Christoph Hellwig" <hch@infradead.org>,
netdev@vger.kernel.org
Subject: Re: Proposed interface for per-packet mesh-ttl
Date: Mon, 30 Jul 2007 13:37:20 -0700 [thread overview]
Message-ID: <445f43ac0707301337l2f7d62ebx6955a12cd89c6bd3@mail.gmail.com> (raw)
In-Reply-To: <20070728073145.57155e03@oldman>
Hi Stephen,
On 7/27/07, Stephen Hemminger <shemminger@linux-foundation.org> wrote:
> In this case perhaps you can have a table that maps skb->priority to
> mesh ttl? priorty can already by handled by existing setsockopt calls,
> and modified by netfilter and QoS managements.
Thanks for the feedback. IMHO overloading the [SOL_SOCKET]
SO_PRIORITY sockoption for something as different as changing the
mesh-ttl is quite a stretch. But I admit that it meets the driver
requirements of "never add sockopt" and "not [ab]use netfilter hooks".
If that's acceptable to all, I'll modify the patch in that direction.
Cheers,
Javier
next prev parent reply other threads:[~2007-07-30 20:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <445f43ac0707031149o2b50fc0en48aef4130b4b60ec@mail.gmail.com>
2007-07-03 19:29 ` Proposed interface for per-packet mesh-ttl Javier Cardona
2007-07-25 20:58 ` Dan Williams
2007-07-27 19:56 ` Christoph Hellwig
2007-07-27 22:22 ` Dan Williams
2007-07-28 6:31 ` Stephen Hemminger
2007-07-30 20:37 ` Javier Cardona [this message]
2007-07-30 20:53 ` Stephen Hemminger
2007-08-16 19:21 ` Luis Carlos Cobo
2007-08-16 21:19 ` Stephen Hemminger
2007-08-16 22:43 ` Luis Carlos Cobo
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=445f43ac0707301337l2f7d62ebx6955a12cd89c6bd3@mail.gmail.com \
--to=javier@cozybit.com \
--cc=dcbw@redhat.com \
--cc=hch@infradead.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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 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).