linux-kernel - Re: RFC: issues concerning the next NAPI interface

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:	Fri, 24 Aug 2007 19:10:43 -0700
From:	"Mitchell Erblich" <erblichs@...thlink.net>
To:	"Jan-Bernd Themann" <ossthema@...ibm.com>
Cc:	"linux-kernel" <linux-kernel@...r.kernel.org>
Subject: Re: RFC: issues concerning the next NAPI interface

Jan-Bernd Themann,

                  IMO, a box must be aware of the speed of all its
interfaces, whether the
                  interface impliments tail-drop or RED or XYZ, the latency
to access the
                  packet, etc.

                  Then when a packet arrives, a timer is started for
interrupt colelesing,
                  and to process awaiting packets, if tail-drop is
implemented, it is
                  possible to wait until a the input FIFO fills to a
specific point before
                  starting a timer.

                  This may maximize the number of packets per interupt. And
realize that
                  the worse case of a interrupt per packet is wirespeed
pings (echo
                  request/reply) of 64 bytes per packet.

                   Mitchell Erblich




-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/