From: David Miller <davem@davemloft.net>
To: ilpo.jarvinen@helsinki.fi
Cc: netdev@vger.kernel.org
Subject: Re: Suspicious fackets_out handling
Date: Mon, 02 Jul 2007 22:07:50 -0700 (PDT) [thread overview]
Message-ID: <20070702.220750.108808313.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0706011417430.28601@kivilampi-30.cs.helsinki.fi>
From: "Ilpo_Järvinen" <ilpo.jarvinen@helsinki.fi>
Date: Fri, 1 Jun 2007 15:17:00 +0300 (EEST)
> On Thu, 31 May 2007, David Miller wrote:
>
> > Is it possible to update fastpath_cnt_hint properly perhaps?
>
> I think that would be valid and even accurate as it can checks skb's
> seq against fastpath_skb_hint->seq. I'm in a hurry and will be a week
> out of reach of internet connectivity but here's quick attempt to deal
> with this cleanly. Compile tested (be extra careful with this one, it's
> done i a hurry :-)), consider to net-2.6. Considering the marginality of
> this issue, stable might really be an overkill for this one, only a
> remotely valid concern comes to my mind in this case: possibility
> of fackets_out > packet_out might not be dealt that cleanly everywhere
> (but I'm sure that you can come to a good decicion about it):
>
> [PATCH] [TCP]: SACK fastpath did override adjusted fackets_out
>
> Do same adjustment to SACK fastpath counters provided that
> they're valid.
>
> Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@helsinki.fi>
Since the case is marginal and the patch does need some testing
I'm putting this into net-2.6.23 for now.
prev parent reply other threads:[~2007-07-03 5:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-23 11:28 Suspicious fackets_out handling Ilpo Järvinen
2007-05-31 19:59 ` David Miller
2007-06-01 12:17 ` Ilpo Järvinen
2007-07-03 5:07 ` David Miller [this message]
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=20070702.220750.108808313.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ilpo.jarvinen@helsinki.fi \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).