All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Graf <tgraf@suug.ch>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 1/3] [IPv4]: FIB configuration using struct fib_config
Date: Wed, 9 Aug 2006 01:11:03 +0200	[thread overview]
Message-ID: <20060808231102.GT14627@postel.suug.ch> (raw)
In-Reply-To: <20060808194600.996388029@postel.suug.ch>

* Thomas Graf <tgraf@suug.ch> 2006-08-08 00:00
> Introduces struct fib_config replacing the ugly struct kern_rta
> prone to ordering issues. Avoids creating faked netlink messages
> for auto generated routes or requests via ioctl.
> 
> A new interface net/nexthop.h is added to help navigate through
> nexthop configuration arrays.
> 
> Since the netlink source pid of the requesting process is stored
> in fib_config, it is no longer required to pass netlink_skb_parms
> all along just for event notification.

Hold on with this patch, netlink pid handling for netlink events
is completely inconsistent. I want to figure out the right way
to do it first.

  reply	other threads:[~2006-08-08 23:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-08 19:38 [PATCHSET] IPv4 FIB configuration rework Thomas Graf
2006-08-07 22:00 ` [PATCH 1/3] [IPv4]: FIB configuration using struct fib_config Thomas Graf
2006-08-08 23:11   ` Thomas Graf [this message]
2006-08-08 23:12     ` David Miller
2006-08-07 22:00 ` [PATCH 2/3] [IPv4]: Convert FIB dumping to use new netlink api Thomas Graf
2006-08-07 22:00 ` [PATCH 3/3] [IPv4]: Convert route get to " Thomas Graf
  -- strict thread matches above, loose matches on Subject: below --
2006-08-15 14:57 [PATCHSET] IPv4 FIB configuration conversions Thomas Graf
2006-08-14 22:00 ` [PATCH 1/3] [IPv4]: FIB configuration using struct fib_config Thomas Graf

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=20060808231102.GT14627@postel.suug.ch \
    --to=tgraf@suug.ch \
    --cc=davem@davemloft.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.