From: Christoph Hellwig <hch@infradead.org>
To: Javier Cardona <javier@cozybit.com>
Cc: netdev@vger.kernel.org
Subject: Re: Proposed interface for per-packet mesh-ttl
Date: Fri, 27 Jul 2007 20:56:16 +0100 [thread overview]
Message-ID: <20070727195616.GA31510@infradead.org> (raw)
In-Reply-To: <445f43ac0707031229m4ed60e0cg7960437c3e373c8e@mail.gmail.com>
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.
next prev parent reply other threads:[~2007-07-27 19:56 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 [this message]
2007-07-27 22:22 ` Dan Williams
2007-07-28 6:31 ` Stephen Hemminger
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=20070727195616.GA31510@infradead.org \
--to=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 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).