netdev - Re: [PATCH] NET: Multiqueue network device support.

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 27 Jun 2007 17:31:39 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	hadi@...erus.ca
Cc:	yi.zhu@...el.com, kaber@...sh.net, peter.p.waskiewicz.jr@...el.com,
	netdev@...r.kernel.org, jeff@...zik.org, auke-jan.h.kok@...el.com
Subject: Re: [PATCH] NET: Multiqueue network device support.

From: jamal <hadi@...erus.ca>
Date: Wed, 27 Jun 2007 20:15:47 -0400

> On Wed, 2007-27-06 at 15:54 -0700, David Miller wrote:
> 
> > The thing that's really important is that the value is not so
> > large such that the TX ring can become empty.
> 
> In the case of batching, varying the values makes a difference.
> The logic is that if you can tune it so that the driver takes
> "sufficiently long" to stay closed the more packets you accumulate at
> the qdisc and the more you can batch to the driver (when it opens up). 
> Deciding what "sufficiently long" is an art - and i am sure speed
> dependent. With e1000 at gige 128 seems to be a good value, going above
> or below that gave lesser performance.

Right.  And another thing you want to moderate is lock hold
times, perhaps even at the slight expense of performance.
-
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