| To: | Mitch Williams <mitch.a.williams@xxxxxxxxx> |
|---|---|
| Subject: | Re: RFC: NAPI packet weighting patch |
| From: | jamal <hadi@xxxxxxxxxx> |
| Date: | Fri, 27 May 2005 07:18:52 -0400 |
| Cc: | netdev@xxxxxxxxxxx, john.ronciak@xxxxxxxxx, ganesh.venkatesan@xxxxxxxxx, jesse.brandeburg@xxxxxxxxx |
| In-reply-to: | <Pine.CYG.4.58.0505261406210.2364@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> |
| Organization: | unknown |
| References: | <Pine.CYG.4.58.0505261406210.2364@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> |
| Reply-to: | hadi@xxxxxxxxxx |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Thu, 2005-26-05 at 14:36 -0700, Mitch Williams wrote: > The following patch (which applies to 2.6.12rc4) adds a new sysctl > parameter called 'netdev_packet_weight'. This parameter controls how many > backlog work units each RX packet is worth. > > With the parameter set to 0 (the default), NAPI polling works exactly as > it does today: each packet is worth one backlog work unit, and the > maximum number of received packets that will be processed in any given > softirq is controlled by the 'netdev_max_backlog' parameter. > NAPI uses already using a Weighted Round robin scheduling scheme know as DRR. I am not sure providing a weight scale on the weight is enhancing anything. Did you try to just reduce the weight instead to make it smaller instead? i.e take the resultant weight of you using a shift and set that as the weight. cheers, jamal |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [8/10] [IPSEC] Use NLMSG_LENGTH in xfrm_exp_state_notify, Herbert Xu |
|---|---|
| Next by Date: | [9/10] Not quite..., Herbert Xu |
| Previous by Thread: | RFC: NAPI packet weighting patch, Robert Olsson |
| Next by Thread: | Re: RFC: NAPI packet weighting patch, Stephen Hemminger |
| Indexes: | [Date] [Thread] [Top] [All Lists] |