netdev - Re: [PATCH net-next v4] rps: selective flow shedding during softnet overflow

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-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20130423.183436.1282688375322312690.davem@davemloft.net>
Date:	Tue, 23 Apr 2013 18:34:36 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	stephen@...workplumber.org
Cc:	eric.dumazet@...il.com, willemb@...gle.com, netdev@...r.kernel.org
Subject: Re: [PATCH net-next v4] rps: selective flow shedding during
 softnet overflow

From: Stephen Hemminger <stephen@...workplumber.org>
Date: Tue, 23 Apr 2013 14:52:22 -0700

> I just don't want to get tied down to one hard coded policy.  User
> seem have different ideas about what constitutes a flow and what
> policy for drop should be.  Existing ingress qdisc is inflexible and
> ifb is a pain to setup and adds another queue transistion.

There is no hard coded policy.

User defines his policy by what cpu he executes his socket reads and
writes upon, and RFS reacts in kind.
--
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