All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael T. Babcock" <mbabcock@fibrespeed.net>
To: lartc@vger.kernel.org
Subject: [LARTC] Prioritizing streams
Date: Thu, 12 Jul 2001 19:36:45 +0000	[thread overview]
Message-ID: <marc-lartc-99496671222537@msgid-missing> (raw)

I have two servers on a network that need to intercommunicate a lot 
(file sharing and authentication information).  I'd like to prioritise 
that traffic on them from their other network traffic, but I don't want 
to think in terms of necessarily fixing bandwidths; I just want the 
inter-server communication to go out first if there's a backlog.

I could decide, I guess, what the minimum level of service for other 
client machines is (say, 5Mbit) and set up two queues -- both unbounded 
-- one for inter-server, one for clients, but with a higher priority on 
the server queue.  Would this work as I expect it to?

-- 
Michael T. Babcock
CTO, FibreSpeed



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

             reply	other threads:[~2001-07-12 19:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-12 19:36 Michael T. Babcock [this message]
2001-07-13  2:03 ` [LARTC] Prioritizing streams Nikolai Vladychevski

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-99496671222537@msgid-missing \
    --to=mbabcock@fibrespeed.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.