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>] [thread-next>] [day] [month] [year] [list]
Message-Id: <266BF78D-5C37-40E1-A065-1426CC2325E2@gmail.com>
Date:	Tue, 1 Sep 2015 23:07:00 +0200
From:	footplus@...il.com
To:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Prioritize a vlan on another

Hello,

I'm not sure if this is the right place to ask this, but i'm stuck on a trafic priority problem since some time.

I have 2 10Gb interfaces (bnx2x) bonded in a 802.3ad aggregate. On this aggregate, 2 vlans are configured (let's INT and EXT) I need to ensure that, when sending traffic at near line rate via EXT, all packets targeted to INT are sent in priority (dropping EXT traffic as needed).

My devices have the mq qdisc by default (running CentOS 7, kernel 3.10).

After googling for documentation about the mq qdisc, I saw it was a stub to have one root qdisc per tx queue, so I expected that below were standard pfifo_fast qdiscs and that I should be able to just mark traffic as Minimize-Delay via iptable's TOS target, but it seems that it has no visible effect when mq+pfifo_fast are in effect.

I played with various qdiscs, and I think I got the right behavior when replacing the mq root qdisc by a prio qdisc (along with using TOS target), but then I was loosing the per-queue lock aspect of the mq qdisc. I did not manage to reproduce this with mq yet.

Could you recommend a way of achieving my goal with the maximum performance ?

Should more details be needed about my setup, i'll collect and send them.

Thanks for your help,

Best regards,
-- 
Aurélien--
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