From: David Miller <davem@davemloft.net>
To: lachlan.andrew@gmail.com
Cc: jheffner@psc.edu, ilpo.jarvinen@helsinki.fi,
netdev@vger.kernel.org, quetchen@caltech.edu
Subject: Re: SACK scoreboard
Date: Tue, 08 Jan 2008 22:35:37 -0800 (PST) [thread overview]
Message-ID: <20080108.223537.03265671.davem@davemloft.net> (raw)
In-Reply-To: <aa7d2c6d0801081734t363768ffi31adb3bd26e639c7@mail.gmail.com>
From: "Lachlan Andrew" <lachlan.andrew@gmail.com>
Date: Tue, 8 Jan 2008 17:34:03 -0800
> John also suggested freeing the packets as a lower priority task, just
> doing it after they're acknowledged.
>
> When the ACK finally comes, you could do something like moving John's
> entire list of packets to a "to be freed" list, and free a few every
> time (say) another ACK comes in.
You could, but this requires extra state and the operations to
properly queue such items to the deferred task and wake it up.
And none of this would be necessary if we could make SACK
indications hard.
next prev parent reply other threads:[~2008-01-09 6:35 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aa7d2c6d0711261023m3d2dd850o76a8f44aef022f39@mail.gmail.com>
[not found] ` <001001c83063$9adbc9d0$d5897e82@csp.uiuc.edu>
2007-11-28 23:47 ` [PATCH] tcp-illinois: incorrect beta usage Stephen Hemminger
2007-11-29 0:25 ` Lachlan Andrew
2007-11-29 0:43 ` Stephen Hemminger
2007-11-29 5:26 ` Shao Liu
2007-12-03 22:52 ` [RFC] TCP illinois max rtt aging Stephen Hemminger
2007-12-03 23:06 ` Lachlan Andrew
2007-12-03 23:59 ` Shao Liu
2007-12-04 0:32 ` Stephen Hemminger
2007-12-04 1:23 ` Lachlan Andrew
2007-12-04 8:37 ` Ilpo Järvinen
2007-12-07 3:27 ` Lachlan Andrew
2007-12-07 11:05 ` Ilpo Järvinen
2007-12-07 12:41 ` David Miller
2007-12-07 13:05 ` Ilpo Järvinen
2007-12-07 18:27 ` Ilpo Järvinen
2007-12-08 1:32 ` David Miller
2007-12-11 11:59 ` [RFC PATCH net-2.6.25 uncompilable] [TCP]: Avoid breaking GSOed skbs when SACKed one-by-one (Was: Re: [RFC] TCP illinois max rtt aging) Ilpo Järvinen
2007-12-11 12:32 ` [RFC PATCH net-2.6.25 uncompilable] [TCP]: Avoid breaking GSOed skbs when SACKed one-by-one David Miller
2007-12-12 0:14 ` Lachlan Andrew
2007-12-12 15:11 ` David Miller
2007-12-12 23:35 ` Lachlan Andrew
2007-12-12 23:38 ` David Miller
2007-12-13 0:00 ` Stephen Hemminger
2007-12-15 9:51 ` SACK scoreboard (Was: Re: [RFC PATCH net-2.6.25 uncompilable] [TCP]: Avoid breaking GSOed skbs when SACKed one-by-one) Ilpo Järvinen
2008-01-08 7:36 ` SACK scoreboard David Miller
2008-01-08 12:12 ` Ilpo Järvinen
2008-01-09 7:58 ` David Miller
2008-01-08 16:51 ` John Heffner
2008-01-08 22:44 ` David Miller
2008-01-09 1:34 ` Lachlan Andrew
2008-01-09 6:35 ` David Miller [this message]
2008-01-09 2:25 ` Andi Kleen
2008-01-09 4:27 ` John Heffner
2008-01-09 6:41 ` David Miller
2008-01-09 14:56 ` John Heffner
2008-01-09 18:14 ` SANGTAE HA
2008-01-09 18:23 ` John Heffner
2008-01-09 12:55 ` Ilpo Järvinen
2008-01-09 6:39 ` David Miller
2008-01-09 7:03 ` Andi Kleen
2008-01-09 7:16 ` David Miller
2008-01-09 9:47 ` Evgeniy Polyakov
2008-01-09 14:02 ` Andi Kleen
2007-11-29 14:12 ` [PATCH] tcp-illinois: incorrect beta usage Herbert Xu
2008-01-09 6:04 SACK scoreboard linux
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=20080108.223537.03265671.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=jheffner@psc.edu \
--cc=lachlan.andrew@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=quetchen@caltech.edu \
/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).