mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stelian Pop <stelian.pop@fr.alcove.com>
To: James Morris <jmorris@intercode.com.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.2 networking, NET_BH latency
Date: Tue, 10 Dec 2002 16:56:32 +0100	[thread overview]
Message-ID: <20021210155632.GC23479@laguna.alcove-fr> (raw)
In-Reply-To: <Mutt.LNX.4.44.0212110245180.1678-100000@blackbird.intercode.com.au>

On Wed, Dec 11, 2002 at 02:46:11AM +1100, James Morris wrote:

> On Tue, 10 Dec 2002, Stelian Pop wrote:
> 
> > I experience some odd behaviour when routing some network packets
> > on a 2.2(.18) kernel (with Ingo's low latency patch in case it 
> > matters).
> > 
> > Although there are probably bugs in the modifications we made
> > (a network card driver, some tweaks in the network core to deal
> > with several packet priorities etc), I'm not sure the behaviour
> > is directly due to a bug in our modifications or some synchronisation
> > issue we overlooked.
> 
> Can you reproduce the problem with a vanilla 2.2.23 kernel?

I didn't try yet, but it is on my list.

Should I interpret your message as some changes between 2.2.18 and 2.2.23
could be responsible for that behaviour or you are just shooting in the
dark ? :-)

Stelian.
-- 
Stelian Pop <stelian.pop@fr.alcove.com>
Alcove - http://www.alcove.com

  reply	other threads:[~2002-12-10 15:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-10 15:31 Stelian Pop
2002-12-10 15:46 ` James Morris
2002-12-10 15:56   ` Stelian Pop [this message]
2002-12-10 15:57     ` James Morris
2002-12-10 16:01       ` Stelian Pop
2002-12-10 21:02 ` David S. Miller
2002-12-10 20:42   ` Stelian Pop
  -- strict thread matches above, loose matches on Subject: below --
2002-11-23 11:42 Stelian Pop

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=20021210155632.GC23479@laguna.alcove-fr \
    --to=stelian.pop@fr.alcove.com \
    --cc=jmorris@intercode.com.au \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®