All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: grzegorz.nosek@netart.pl
Cc: linux-kernel@vger.kernel.org
Subject: Re: Very slow routing table modification if RTA_FLOW is set
Date: Thu, 01 Mar 2007 10:35:32 -0800 (PST)	[thread overview]
Message-ID: <20070301.103532.130237452.davem@davemloft.net> (raw)
In-Reply-To: <20070301142911.GA8187@tech.serwery.pl>

From: NetArt - Grzegorz Nosek <grzegorz.nosek@netart.pl>
Date: Thu, 1 Mar 2007 15:29:11 +0100

> I have noticed that using realm patch for quagga
> <http://vcalinus.gemenii.ro/quaggarealms.html> causes the kernel to
> spend a lot more time processing rtnetlink messages.

Please report networking problems to the networking development
list which is netdev@vger.kernel.org, thank you.

Most networking developers do not read linux-kernel.

  reply	other threads:[~2007-03-01 18:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-01 14:29 Very slow routing table modification if RTA_FLOW is set NetArt - Grzegorz Nosek
2007-03-01 18:35 ` David Miller [this message]
2007-03-02 19:28 ` David Miller
  -- strict thread matches above, loose matches on Subject: below --
2007-03-01 14:29 NetArt - Grzegorz Nosek

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=20070301.103532.130237452.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=grzegorz.nosek@netart.pl \
    --cc=linux-kernel@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.