From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Dan Williams <dcbw@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Javier Cardona <javier@cozybit.com>,
netdev@vger.kernel.org
Subject: Re: Proposed interface for per-packet mesh-ttl
Date: Sat, 28 Jul 2007 07:31:45 +0100 [thread overview]
Message-ID: <20070728073145.57155e03@oldman> (raw)
In-Reply-To: <1185574942.17934.9.camel@xo-13-A4-25.localdomain>
On Fri, 27 Jul 2007 18:22:22 -0400
Dan Williams <dcbw@redhat.com> wrote:
> On Fri, 2007-07-27 at 20:56 +0100, Christoph Hellwig wrote:
> > On Tue, Jul 03, 2007 at 12:29:24PM -0700, Javier Cardona wrote:
> > > I'm currently working on per-packet mesh ttl. My plan is to register
> > > new mesh sockopts through netfilter. The user interface will be:
> >
> > NACK. Drivers should never add sockopt, and drivers should not abuse
> > netfilter hooks.
>
> Do you have a suggestion for a better way to approach per-packet options
> that userspace programs can set?
>
> Thanks,
> Dan
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.
next prev parent reply other threads:[~2007-07-28 6:31 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 [this message]
2007-07-30 20:37 ` Javier Cardona
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=20070728073145.57155e03@oldman \
--to=shemminger@linux-foundation.org \
--cc=dcbw@redhat.com \
--cc=hch@infradead.org \
--cc=javier@cozybit.com \
--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.