All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: baruch@ev-en.org
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 3/3] Check num sacks in SACK fast path
Date: Sun, 04 Feb 2007 23:38:03 -0800 (PST)	[thread overview]
Message-ID: <20070204.233803.97293382.davem@davemloft.net> (raw)
In-Reply-To: <20070202144127.26863.97696.sendpatchset@galon.ev-en.org>

From: Baruch Even <baruch@ev-en.org>
Date: Fri, 02 Feb 2007 16:41:27 +0200

> We clear the unused parts of the SACK cache, This prevents us from mistakenly
> taking the cache data if the old data in the SACK cache is the same as the data
> in the SACK block. This assumes that we never receive an empty SACK block with
> start and end both at zero.
> 
> Signed-Off-By: Baruch Even <baruch@ev-en.org>

I've applied this one too, thanks a lot.

  parent reply	other threads:[~2007-02-05  7:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070202144116.26863.3722.sendpatchset@galon.ev-en.org>
2007-02-05  7:36 ` [PATCH 1/3] Advance fast path pointer for first block only David Miller
     [not found] ` <20070202144121.26863.90947.sendpatchset@galon.ev-en.org>
2007-02-05  7:36   ` [PATCH 2/3] Seperate DSACK from SACK fast path David Miller
     [not found] ` <20070202144127.26863.97696.sendpatchset@galon.ev-en.org>
2007-02-05  7:38   ` David Miller [this message]
     [not found] <20070129071339.24050.21052.sendpatchset@galon.ev-en.org>
     [not found] ` <20070129071349.24050.56022.sendpatchset@galon.ev-en.org>
2007-01-31 20:52   ` [PATCH 3/3] Check num sacks in " David Miller
2007-02-01  7:22     ` Baruch Even
2007-02-01 22:38       ` David Miller
2007-01-27 16:47 [PATCH 0/3] Fix issues with SACK processing Baruch Even
2007-01-27 16:50 ` [PATCH 3/3] Check num sacks in SACK fast path Baruch Even

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=20070204.233803.97293382.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=baruch@ev-en.org \
    --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 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.