public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: "David S. Miller" <davem@redhat.com>
Cc: ak@suse.de, sim@netnation.com, linux-kernel@vger.kernel.org,
	linux-net@vger.kernel.org
Subject: Re: Longstanding networking / SMP issue? (duplextest)
Date: Fri, 21 Feb 2003 08:27:19 +0100	[thread overview]
Message-ID: <20030221072719.GD25144@wotan.suse.de> (raw)
In-Reply-To: <20030220.202438.10564686.davem@redhat.com>

On Thu, Feb 20, 2003 at 08:24:38PM -0800, David S. Miller wrote:
>    From: Andi Kleen <ak@suse.de>
>    Date: Thu, 20 Feb 2003 10:34:22 +0100
> 
>    On Thu, Feb 20, 2003 at 01:20:43AM -0800, Simon Kirby wrote:
>    > Hmm...and this is considered desired behavior?  It seems like an odd way
>    > of handling packets intended to test latency and reliability. :)
>    
>    IP is best-effort. Dropping packets in odd cases to make locking simpler
>    is not unreasonable. Would you prefer an slower kernel?
> 
> True.
> 
> But this is a quality of implementation issue and I doubt the kernel
> would be slower if we fixed this silly behavior.
> 
> Frankly, the locking is due to lazyness, rather than a specific design
> decision.  So let's fix it.

For icmp_xmit_lock it can be only done in a limited fashion - you are
always restricted by the buffer size of the ICMP socket. Also I don't 
know how to lock the socket from BH context nicely - the only simple way
probably is the trick from the retransmit timer to just try again
in a jiffie, but could have nasty queueing up under high load.

Fixing the error drop behaviour of TCP will be somewhat nasty too.

In both cases you'll need a retry timer (unreliable) or an dedicated ICMP 
backlog (complicated)

-Andi

  reply	other threads:[~2003-02-21  7:17 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030219174757.GA5373@netnation.com.suse.lists.linux.kernel>
2003-02-20  7:52 ` Longstanding networking / SMP issue? (duplextest) Andi Kleen
2003-02-20  7:38   ` David S. Miller
2003-02-20  9:20   ` Simon Kirby
2003-02-20  9:34     ` Andi Kleen
2003-02-20 10:12       ` dada1
2003-02-20 10:54         ` Andi Kleen
2003-02-20 11:03           ` dada1
2003-02-21  4:24       ` David S. Miller
2003-02-21  7:27         ` Andi Kleen [this message]
2003-02-21  9:43           ` David S. Miller
2003-02-21 10:22             ` Andi Kleen
2003-02-21 10:11               ` David S. Miller
2003-02-21 10:45                 ` Andi Kleen
2003-02-23  9:12                   ` David S. Miller
2003-02-23 10:02                     ` Christoph Hellwig
2003-02-23  9:55                       ` David S. Miller
2003-02-23 10:30                         ` Andi Kleen
2003-02-23 10:23                           ` David S. Miller
2003-02-23 10:37                           ` Christoph Hellwig
2003-02-23  9:58                       ` David S. Miller
2003-02-21 15:15       ` Bill Davidsen
2003-02-19 17:47 Simon Kirby
2003-02-19 21:17 ` David S. Miller

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=20030221072719.GD25144@wotan.suse.de \
    --to=ak@suse.de \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=sim@netnation.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