From: David Miller <davem@davemloft.net>
To: shemminger@linux-foundation.org
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 4/4]: Kill fastpath_{skb,cnt}_hint.
Date: Wed, 28 Feb 2007 13:12:17 -0800 (PST) [thread overview]
Message-ID: <20070228.131217.92582224.davem@davemloft.net> (raw)
In-Reply-To: <20070228130808.4b7a9ea8@localhost.localdomain>
From: Stephen Hemminger <shemminger@linux-foundation.org>
Date: Wed, 28 Feb 2007 13:08:08 -0800
> I would be happy to see this go. Have you tried this code with
> a SACK DoS stream? I.e. before you could consume a huge amount
> of cpu time by giving an certain bad sequence of SACK's. This
> code should have a better worst case run time.
No I didn't do that.
In fact this new code wedged my workstation overnight somehow
and I need to debug that at some point as well. :-)
next prev parent reply other threads:[~2007-02-28 21:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-28 19:49 [PATCH 4/4]: Kill fastpath_{skb,cnt}_hint David Miller
2007-02-28 21:08 ` Stephen Hemminger
2007-02-28 21:12 ` David Miller [this message]
2007-03-01 18:13 ` Baruch Even
2007-03-03 6:22 ` David Miller
2007-03-03 8:12 ` Baruch Even
2007-03-03 11:45 ` Ilpo Järvinen
2007-03-03 12:27 ` Ilpo Järvinen
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=20070228.131217.92582224.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox