From: Danial Thom <danial_thom@yahoo.com>
To: Patrick McHardy <kaber@trash.net>
Cc: Sven-Thorsten Dietrich <sven@mvista.com>,
Helge Hafting <helge.hafting@aitel.hist.no>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.12 Performance problems
Date: Wed, 24 Aug 2005 09:39:46 -0700 (PDT) [thread overview]
Message-ID: <20050824163946.94088.qmail@web33301.mail.mud.yahoo.com> (raw)
In-Reply-To: <430B89BE.1020600@trash.net>
--- Patrick McHardy <kaber@trash.net> wrote:
> Danial Thom wrote:
> > None of this is helpful, but since no one has
> > been able to tell me how to tune it to
> provide
> > absolute priority to the network stack I'll
> > assume it can't be done.
>
> The network stack already has priority over
> user processes,
> except when executed in process context, so
> preemption has
> no direct impact on briding or routing
> performance.
>
> The reason why noone answered your question is
> because you
> don't ask but claim or assume.
>
No, its because guys like you snip out content
when they reply, and/or only read the parts of
messages that you want to read, so when other
people enter a thread, they miss the questions
that were asked long ago. Quoting my post on Aug
22:
"All of this aside, I need to measure the raw
capabilities of the kernel. With 'bsd OSes I can
tell what the breaking point is by driving the
machine to livelock. Linux seems to have a soft,
floating capacity in that it will drop packets
here and there for no isolatable reason. I'm
having difficulty making a case for its use in a
networking appliance, as dropped packets are not
acceptable. How do I tune the "its ok to drop
packets when x occurs" algorithm to be "its never
ok to drop packets unless x occurs" (such as a
queue depth)? Is it possible?"
Danial
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
next prev parent reply other threads:[~2005-08-24 16:39 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-21 16:57 Danial Thom
2005-08-23 7:12 ` Helge Hafting
2005-08-23 17:10 ` Danial Thom
2005-08-23 17:21 ` Patrick McHardy
2005-08-24 16:24 ` Danial Thom
2005-08-24 16:35 ` Jesper Juhl
2005-08-24 17:26 ` Danial Thom
2005-08-25 4:51 ` Ben Greear
2005-08-25 6:08 ` Danial Thom
2005-08-25 6:15 ` Ben Greear
2005-08-26 3:29 ` Danial Thom
2005-08-26 22:18 ` Danial Thom
2005-08-25 6:34 ` Ben Greear
2005-08-25 14:26 ` Danial Thom
2005-08-25 16:55 ` Ben Greear
2005-08-25 20:45 ` Danial Thom
2005-08-26 19:10 ` Benjamin LaHaise
2005-08-27 11:19 ` Vladimir B. Savkin
2005-08-27 14:35 ` Danial Thom
2005-08-23 18:02 ` Sven-Thorsten Dietrich
2005-08-23 20:10 ` Danial Thom
2005-08-23 20:22 ` Sven-Thorsten Dietrich
2005-08-24 16:33 ` Danial Thom
2005-08-23 20:40 ` Patrick McHardy
2005-08-23 23:29 ` Ben Greear
2005-08-24 16:39 ` Danial Thom [this message]
2005-08-23 21:32 ` Jesper Juhl
2005-08-24 17:03 ` Danial Thom
[not found] <2230.192.167.206.189.1124721719.squirrel@new.host.name>
2005-08-22 15:41 ` Danial Thom
2005-08-26 13:17 ` Adrian Bunk
2005-08-26 15:34 ` Danial Thom
2005-08-26 16:21 ` Adrian Bunk
2005-08-26 17:06 ` Danial Thom
2005-08-26 18:30 ` Adrian Bunk
2005-08-26 21:09 ` Danial Thom
2005-08-26 23:27 ` Ben Greear
2005-08-27 14:44 ` Danial Thom
[not found] <9a87484905082111205d27c1aa@mail.gmail.com>
2005-08-21 20:21 ` Danial Thom
2005-08-21 21:21 ` Jesper Juhl
2005-08-22 11:46 ` Denis Vlasenko
-- strict thread matches above, loose matches on Subject: below --
2005-08-21 17:07 Danial Thom
2005-08-21 15:46 Danial Thom
2005-08-21 16:15 ` Patrick McHardy
2005-08-21 16:18 ` Danial Thom
2005-08-21 16:36 ` Patrick McHardy
2005-08-21 19:47 ` Andrew Morton
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=20050824163946.94088.qmail@web33301.mail.mud.yahoo.com \
--to=danial_thom@yahoo.com \
--cc=helge.hafting@aitel.hist.no \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sven@mvista.com \
/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
all inboxes | Powered by JetHome®