All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mihai RUSU <dizzy@roedu.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] sfq, queue len and dropped packets
Date: Fri, 12 Apr 2002 06:55:56 +0000	[thread overview]
Message-ID: <marc-lartc-101859414108263@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101845196916261@msgid-missing>

On Thu, 11 Apr 2002, Don Cohen wrote:

> One example is that you have two interfaces, one is limited (either by
> hardware or software) to 10Mbps and the other to 1Mbps.  Then if
> traffic arrives on the faster one at, say, 2Mbps, you clearly won't be
> able to forward it all out the slower one.  In that case you'd end up
> with lots of dropped packets and long queues.
>

Hmm, my setup has one fast eth incoming interface (no outgoing at all on
that interface) and one outgoing fast eth interface (there is no incoming
traffic on this one). They use the same driver and are very good hardware
(eepro100).

> Unless you have either an unusually fast network or an unusually slow
> computer, the bottleneck is more likely in the network than the cpu.
>

Oh, so 100Mbit its no problem for a 2xP3 1GHz ? :)

>  > I usually dont have problems hacking into C programms but I dont get it
>  > what does that comment means, with the 4k page limit. I mean I need a
>  > formula to calculate to see if I would get over that 4k limit.
> I think that increasing the 128 will require you to change the type
> from char to int.  One of those arrays has 2 * sfq_depth elements.
> The code could be fixed to not require changing the type until you
> go over sfq_depth 256, but I think it'll be easier for you to just
> change the type and not worry about it.
>

Ok, I'll look into it, thanks.

----------------------------
Mihai RUSU

Disclaimer: Any views or opinions presented within this e-mail are solely
those of the author and do not necessarily represent those of any company,
unless otherwise specifically stated.

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2002-04-12  6:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-10 15:26 [LARTC] sfq, queue len and dropped packets Mihai RUSU
2002-04-10 16:19 ` Stef Coene
2002-04-10 18:55 ` Don Cohen
2002-04-11 18:17 ` Mihai RUSU
2002-04-11 18:33 ` Don Cohen
2002-04-12  6:55 ` Mihai RUSU [this message]

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=marc-lartc-101859414108263@msgid-missing \
    --to=dizzy@roedu.net \
    --cc=lartc@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.