lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:	Thu, 18 Jun 2009 13:13:00 +0900
From:	Minoru Usui <usui@....nes.nec.co.jp>
To:	"Chei-Yol Kim" <gauri@...i.re.kr>
Cc:	<netdev@...r.kernel.org>, <containers@...ts.linux-foundation.org>,
	<tgraf@...radead.org>
Subject: Re: [HELP] for using class group classifier network controller

> when I set the classid to 0x10010, class 1:10's packet count was increased. 
> But, according to your configuration, every packet has to flowed to 1:10 class. 

Yes, you are right.

> Of course I know that the net_cls can't classify all packet because of the getting classid from the current task. 
> Even though we consider it, Many packets are flowed to 1:30 class. 
> therefore, the rate of the socket showed about 30mbps. This is the 1:30 class's rate.
> I think it's because that 1:30 class is the default class. 
> When I changed the default to 20, the rate was varied to 20mbps, class 1:20's rate.
>
> 
> To measure this rate, I used the iperf and scp command. Two results are the same.
> How about your experiment's result? 
> Would you check the accurate rate of the network using applications like a iperf?

I did same experience with nuttcp, I observed the same result, too.
(Almost packets were classified into default classid.)
 
> By the results of my experiments, net_cls couldn't control the network rate of the group. 
> What is your opinion?

I agree with you.
I'm going to investigate this problem. 

-- 
Minoru Usui <usui@....nes.nec.co.jp>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ