From: pravin b shelar <pravin.shelar@calsoftinc.com>
To: Chris Wedgwood <cw@f00f.org>
Cc: netdev@vger.kernel.org, Ravikiran G Thirumalai <kiran@scalex86.org>
Subject: Re: [PATCH] Disable multipath cache routing
Date: Sat, 20 May 2006 15:11:20 +0530 [thread overview]
Message-ID: <446EE440.8000808@calsoftinc.com> (raw)
In-Reply-To: <446ED597.20300@calsoftinc.com>
Chris Wedgwood wrote:
> Apparently IP_ROUTE_MULTIPATH_CACHED isn't entirely safe to use and
> will oops the kernel "sooner or later". The Kconfig comment says
> EXPERIMENTAL but it's not.
>
> Let's go further and mark it BROKEN for now (leaving the comment as-is
> though). If nobody steps up to resurrect this code we can discuss
> removing it entirely.
I am working on Linux multipath networking and I will like to fix bugs
related to equal cost multipath caching support.
So can u send me following information about the oops :-
kernel version
config file
routing table setup ( any multipath setup information. e.g. multipath
algorithm options)
iptable configuration
forwarding information
what was the oops message & what triggered that?
This will help me understand the problem.
Thanks & Regards,
Pravin.
next parent reply other threads:[~2006-05-20 9:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <446ED597.20300@calsoftinc.com>
2006-05-20 9:41 ` pravin b shelar [this message]
2006-05-20 20:51 ` [PATCH] Disable multipath cache routing Chris Wedgwood
2006-05-22 4:55 ` [CFT] CONFIG_IP_ROUTE_MULTIPATH_CACHED [was Re: [PATCH] Disable multipath cache routing ] Ravikiran G Thirumalai
2006-05-20 2:52 [PATCH] Disable multipath cache routing Chris Wedgwood
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=446EE440.8000808@calsoftinc.com \
--to=pravin.shelar@calsoftinc.com \
--cc=cw@f00f.org \
--cc=kiran@scalex86.org \
--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.