netdev - Re: pktgen terminating condition

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: <1188347327.4305.27.camel@localhost>
Date:	Tue, 28 Aug 2007 20:28:47 -0400
From:	jamal <hadi@...erus.ca>
To:	David Miller <davem@...emloft.net>
Cc:	rick.jones2@...com, msb@...gle.com, netdev@...r.kernel.org,
	grundler@...gle.com, robert.olsson@....uu.se, venza@...wnhat.org
Subject: Re: pktgen terminating condition

On Tue, 2007-28-08 at 17:06 -0700, David Miller wrote:

> Devices need to free packets in a deterministic amount of time, no
> matter what.

If i understood the driver pointed to - "finite amount of time" spec is
still met. Seems some interupt is generated (TX_IDLE) when the tx path
gets idle and this will kick the tx cleanup. Mandeep, correct me if i am
wrong. If my statement is correct, i wouldnt call this a driver bug;->

Robert, I think i asked you this same question on that piece of code
once  - and iirc you said its because you had to synchronise and make
sure the packet made it to the wire. In this scenario, the packet has
made it to the wire - just hasnt been freed. Note that when teaching
pktgen to do batching, i removed that logic and things work fine.

cheers,
jamal

-
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