mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: kus Kusche Klaus <kus@keba.com>
Cc: Lee Revell <rlrevell@joe-job.com>, linux-kernel@vger.kernel.org
Subject: RE: My vote against eepro* removal
Date: Thu, 19 Jan 2006 17:57:25 -0500	[thread overview]
Message-ID: <1137711445.6762.116.camel@localhost.localdomain> (raw)
In-Reply-To: <1137697744.6762.106.camel@localhost.localdomain>

On Thu, 2006-01-19 at 14:09 -0500, Steven Rostedt wrote:
> On Thu, 2006-01-19 at 11:26 +0100, kus Kusche Klaus wrote:
> > > From: Lee Revell
> > > On Thu, 2006-01-19 at 08:19 +0100, kus Kusche Klaus wrote:
> > > > Last time I tested (around 2.6.12), eepro100 worked much better 
> > > > in -rt kernels w.r.t. latencies than e100:
> 
> Try the latest -rt kernel with e100 to see if it still is a delay.  You
> can also run in PREEMPT_DESKTOP so that the interrupt handlers are not
> threads and see if that shows up in the latency.

I just booted up 2.6.15-rt6 (PREEMPT_DESKTOP, regular soft and hard
irqs) on a 366 MHz UP machine with init=/bin/bash.  Loaded the e100
driver, setup the network. Then started to ping it from another box.  I
had a 80 usec latency, and that wasn't even from the network card.

So, e100 should not be a problem.  I did see the interrupts go off every
2 seconds too.

Check to see if you still get the latencies with e100 and the latest
kernel.

As Lee already said.  You notice something fishy __PLEASE__ report it.
Arjan's response was that this shows that we should only have one driver
for a certain task, otherwise people wont report a problem with one, if
the other satisfies their needs. And thus, the problem remains.

-- Steve


  reply	other threads:[~2006-01-19 22:57 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-19 10:26 kus Kusche Klaus
2006-01-19 16:20 ` Adrian Bunk
2006-01-19 17:16   ` John Ronciak
2006-01-19 19:09 ` Steven Rostedt
2006-01-19 22:57   ` Steven Rostedt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-01-24  7:38 kus Kusche Klaus
2006-01-23 11:01 kus Kusche Klaus
2006-01-23 20:23 ` Jesse Brandeburg
2006-01-20 11:27 kus Kusche Klaus
2006-01-20 10:51 kus Kusche Klaus
2006-01-20 11:05 ` Evgeniy Polyakov
2006-01-20 10:19 kus Kusche Klaus
2006-01-20 11:02 ` Evgeniy Polyakov
2006-01-21  0:45 ` Lee Revell
2006-01-20  9:37 kus Kusche Klaus
2006-01-20  9:55 ` Evgeniy Polyakov
2006-01-21  0:40   ` Lee Revell
2006-01-21  1:19     ` John Ronciak
2006-01-21  1:30       ` Lee Revell
2006-01-21  2:01         ` John Ronciak
2006-01-21  3:56           ` Lee Revell
2006-01-19 10:08 kus Kusche Klaus
2006-01-19  7:19 kus Kusche Klaus
2006-01-19  7:24 ` Lee Revell
2006-01-19  7:42 ` Arjan van de Ven

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=1137711445.6762.116.camel@localhost.localdomain \
    --to=rostedt@goodmis.org \
    --cc=kus@keba.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.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

Powered by JetHome