All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nickola Kolev <nikky@mnet.bg>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] u32 hash-es ?
Date: Sun, 07 Dec 2003 21:54:49 +0000	[thread overview]
Message-ID: <marc-lartc-107083414301165@msgid-missing> (raw)
In-Reply-To: <marc-lartc-107080042711323@msgid-missing>

[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]

Hello, raptor,

On Sun, 7 Dec 2003 14:11:10 +0200
raptor <raptor@tvskat.net> wrote:

[ cut for simplicity's sake ]

 : I have to change the
 :          hashkey mask 0x000000ff at 13 
 : to :
 :         hashkey mask 0x000000XX at 13  :"), fill in..

Probably 0x40? And btw, you are doing hashes by source IP, right? Why is that -
some kind of ingress filtering? For a dest should this be "at 16"?

 : Subquestion : is there a way to see exactly which subsystem takes what cpu time, on the top/atop 
 : output we see just the total SYSTEM cpu time but now how it is divided by the net framework..
 : if we have such info we will know how to tune the system better ?!

Have you tried sar?

Debian: apt-get install atsar

In general, I could be of no help, but I'm also very much interested in any
replies you receive about a working hash syntax and methodology. Please share
them with us. ;)
________________________________________________________________________

Cheers,
Nickola

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCM d? s:- a- C++++ UL++++ P+ L++++ E--- W-- N o K- w-- 
O- M- V- PS+ PE Y PGP- t 5 X R- tv- b+++ DI-- D+ 
G e h-- r y** 
------END GEEK CODE BLOCK------

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2003-12-07 21:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-07 12:11 [LARTC] u32 hash-es ? raptor
2003-12-07 21:54 ` Nickola Kolev [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-107083414301165@msgid-missing \
    --to=nikky@mnet.bg \
    --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.