From: Ben Greear <greearb@candelatech.com>
To: jamal <hadi@cyberus.ca>
Cc: "'netdev@oss.sgi.com'" <netdev@oss.sgi.com>
Subject: Re: [PATCH] Break 'budget' dependency on netdev_max_backlog.
Date: Tue, 22 Oct 2002 20:43:00 -0700 [thread overview]
Message-ID: <3DB61AC4.4070907@candelatech.com> (raw)
In-Reply-To: Pine.GSO.4.30.0210222317210.24323-100000@shell.cyberus.ca
jamal wrote:
>
> On Tue, 22 Oct 2002, Ben Greear wrote:
>
>
>>Think we should add an IOCTL to change the weight of a device
>>dynamically? (I want my e1000 and tg3 to have higher weight than
>>the tulip nics, I imagine)
>>
>>Is there a ready-built proc interface to do things to individual devices?
>>
>
>
> tulip hardcodes it; net/core/dev.c::weight_p is supposed to be the general
> one and is proc settable via NET_CORE_DEV_WEIGHT; only problem is that
> is not shadowed by the devices.
> I am not sure if ioctls or module parameters are the best way to override
> the default weight_p value. Somehow we need something to set this value.
No reason not to provide both! The IOCTL can take care of any drivers
that don't take module parameters for it, and can do it in a generic
way.
The tulip driver I am poking at hard-coded it to 16. 64 seems to work
just as good.
Any idea (other than trial and error) for how to determine a good value
for this? Maybe should take the number of active devices into account
and wiggle things dynamically from user-space?
Ben
>
> cheers,
> jamal
>
--
Ben Greear <greearb@candelatech.com> <Ben_Greear AT excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
next prev parent reply other threads:[~2002-10-23 3:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 6:46 [PATCH] Break 'budget' dependency on netdev_max_backlog Ben Greear
2002-10-21 12:51 ` jamal
2002-10-21 16:25 ` Ben Greear
2002-10-23 0:47 ` jamal
2002-10-23 1:06 ` Ben Greear
2002-10-23 1:18 ` jamal
2002-10-23 2:37 ` Ben Greear
2002-10-23 3:21 ` jamal
2002-10-23 3:43 ` Ben Greear [this message]
2002-10-23 3:44 ` jamal
2002-10-23 4:00 ` Ben Greear
2002-10-23 3:58 ` jamal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3DB61AC4.4070907@candelatech.com \
--to=greearb@candelatech.com \
--cc=hadi@cyberus.ca \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).