From: ganesh palwe <ganeshpalwe@yahoo.com>
To: lartc@vger.kernel.org
Subject: [LARTC] how to determine tcp rate & classifying packet info
Date: Tue, 21 Jan 2003 20:43:59 +0000 [thread overview]
Message-ID: <marc-lartc-104318194301024@msgid-missing> (raw)
[-- Attachment #1: Type: text/plain, Size: 526 bytes --]
hello everybody
need help
how should i control the tcp rate, is it possible?
also,
suppose i have 2 database tables :
1) one for online accounting &
2) one for online sales updating
now both of these transactions which will update my SQL server databse will be on the same port number
how can i classify these packets so that i can give high bandwidth & highest prio to type 2 packets.
10x in advance.
ganesh.
---------------------------------
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now
[-- Attachment #2: Type: text/html, Size: 763 bytes --]
next reply other threads:[~2003-01-21 20:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-21 20:43 ganesh palwe [this message]
2003-01-21 21:44 ` [LARTC] how to determine tcp rate & classifying packet info Stef Coene
2003-01-22 1:07 ` ganesh palwe
2003-01-22 9:33 ` Jesper Kold-Hansen
2003-01-22 17:11 ` Stef Coene
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-104318194301024@msgid-missing \
--to=ganeshpalwe@yahoo.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox