From: Dan Malek <dan@embeddededge.com>
To: scop@digitel.com.br
Cc: linuxppc-embedded@lists.linuxppc.org, andy_lowe@mvista.com
Subject: Re: Kernel oops while routing
Date: Thu, 29 Nov 2001 17:42:24 -0500 [thread overview]
Message-ID: <3C06B9D0.7020804@embeddededge.com> (raw)
In-Reply-To: 9810.011129@digitel.com.br
Ricardo Scop wrote:
> I'm kind of lost with this performance variations. As far as I could
> see, the patch did not insert much processing overhead, so...
Perhaps if someone would post the patch for the rest of us to see we
could be of some assistance.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-11-29 22:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-26 16:54 Kernel oops while routing Ricardo Scop
2001-11-29 22:27 ` Ricardo Scop
2001-11-29 22:42 ` Dan Malek [this message]
2001-12-05 3:24 ` Re[2]: " Ricardo Scop
2001-12-05 17:56 ` Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2001-12-05 18:01 Jean-Denis Boyer
2001-12-05 18:21 ` Peter Desnoyers
2001-12-05 18:33 ` Dan Malek
2001-12-07 15:56 ` Arto Vuori
2001-12-05 18:38 Jean-Denis Boyer
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=3C06B9D0.7020804@embeddededge.com \
--to=dan@embeddededge.com \
--cc=andy_lowe@mvista.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=scop@digitel.com.br \
/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.