All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John Anthony Kazos Jr." <jkazos@vt.edu>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: TOS useful???
Date: Tue, 27 Mar 2001 03:08:42 +0000	[thread overview]
Message-ID: <marc-lartc-98566248007844@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98546911132362@msgid-missing>

I figure that, in the ideal situation, bandwidth throttling would occur on
a drop-by-drop basis. (That's the only way I can see to do it that can't
be abused, like the TOS fields can, to bring it back to that discussion.
;-)) In that ideal situation, what I plan to do (and, just to un-fluff the
feathers of sys-admins everywhere, at a not--continually-maximal bandiwdth
utilization) is to "reclaim" (read: fully utilize) any bandwidth wasted by
one person not fully using theirs, just as space is wasted if you have two
partitions with a filing system in each, which can't share files, rather
than a single partition, or two filing systems which can combine their
unused space. And by the sharing of services (not bandwidth; services)
amongst different rooms, a greater amount of idleness is maintained on
each, so peaks are taken care of handily, and usage is balanced over the
entire network. (In the *truly* ideal scenario, all users of the entire
network across campus, across a state, in the world, ad infinitum, would
share the same logical bandwidth with no waste. The "real" world is a
subset, or an approximation, of the ideal world.)

On Mon, 26 Mar 2001, Gerry Creager wrote:

> "John Anthony Kazos Jr." wrote:
> > 
> > Of course it does! :P In our dormitory rooms each person is intended to
> > use one 10-Base-T port, but we're going to run a box that connects to both
> > and balances the traffic across both. We're also going to set up similar
> > boxes in our friends' rooms, and balance the *services* between them.
> > We're going to squeeze out every ounce of bandwidth we can.
> > 
> > It's going to be fun, to say the least. :-)
> 
> Arrrrrggggggghhhhhhh!  Folks like you make bandwidth throlling by folks
> like me a necessity, to preserve what we have for the other campus
> users.  We have seen P2P activities drive us to 80+ percent utilization
> at times, with Napster-likes being the bulk thereof.  We've had servers
> and RPGs cause similar load problems, especially when we have a truly
> talented designer/developer pop up.
> 
> This isn't a tirade against the students, more a plea.  We're seeing
> bandwidth demand accellerate beyond our (as network managers') ability
> to increase supply.  Part of this is that bandwidth isn't free... nor
> even cheap... and we have to live on budgets based on what we
> anticipated 18 or so months ago, and the management above us in the food
> chain subsequently cut.  If we guessed wrong in either direction, our
> credibility was screwed and we can't get an increase next year...
> 
> Think about it.  This is a cool _ONE_TIME_ experiment, but if it ramps
> up, expect your name in the student newspaper as one of the reasons the
> bandwidth for your dorm was cut to 56kbps.
> 
> TTFN, gerry
> 


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

  parent reply	other threads:[~2001-03-27  3:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-24 21:23 [LARTC] Re: TOS useful??? bert hubert
2001-03-25  3:57 ` Rogerio Brito
2001-03-25 20:06 ` bert hubert
2001-03-26 11:47 ` Arthur van Leeuwen
2001-03-26 11:59 ` bert hubert
2001-03-26 12:07 ` Arthur van Leeuwen
2001-03-26 14:40 ` Gregory Maxwell
2001-03-26 14:45 ` bert hubert
2001-03-26 14:52 ` John Anthony Kazos Jr.
2001-03-26 23:25 ` Mike Fedyk
2001-03-27  1:29 ` Gerry Creager
2001-03-27  3:08 ` John Anthony Kazos Jr. [this message]
2001-03-27 12:02 ` RoMaN SoFt / LLFB!!
2001-03-29 22:26 ` Mike Fedyk

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-98566248007844@msgid-missing \
    --to=jkazos@vt.edu \
    --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.