From: David Miller <davem@davemloft.net>
To: hch@lst.de
Cc: shemminger@osdl.org, netdev@vger.kernel.org
Subject: Re: [PATCH 2/2] correct dev_alloc_skb kerneldoc
Date: Sat, 08 Jul 2006 13:37:38 -0700 (PDT) [thread overview]
Message-ID: <20060708.133738.123994596.davem@davemloft.net> (raw)
In-Reply-To: <20060708104811.GB31751@lst.de>
From: Christoph Hellwig <hch@lst.de>
Date: Sat, 8 Jul 2006 12:48:12 +0200
> My plan is to give dev_alloc_skb a struct netdevice * argument and
> introduce a alloc_netdev_node so the driver can tell what node the
> device is on. This gives a significant speedup for cell. I already
> have this implemented in fact but only converted a handfull of drivers.
>
> Does this approach sound okay?
I do not think it is feasible to add a netdevice argument to
such a widely used interface.
I would instead recommend that you add a new interface, and
we convert drivers gradually.
That netdevice argument is useful for other things. For example,
you can use it to apply a per-netdev random memory allocation
failure setting, to test the robustness of drivers. I came up
with that idea something like 7 years ago but never got around
to doing it :)
next prev parent reply other threads:[~2006-07-08 20:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-07 9:09 [PATCH 2/2] correct dev_alloc_skb kerneldoc Christoph Hellwig
2006-07-07 22:52 ` Stephen Hemminger
2006-07-07 23:55 ` David Miller
2006-07-08 3:11 ` Herbert Xu
2006-07-08 10:48 ` Christoph Hellwig
2006-07-08 20:37 ` David Miller [this message]
2006-07-13 20:36 ` Christoph Hellwig
2006-07-13 20:47 ` Randy.Dunlap
2006-07-13 20:47 ` David Miller
2006-07-14 15:24 ` chas williams - CONTRACTOR
2006-07-13 21:24 ` Stephen Hemminger
2006-07-13 21:29 ` Christoph Hellwig
2006-07-13 22:01 ` David Miller
2006-07-14 7:27 ` Samuel Ortiz
2006-07-14 6:49 ` Christoph Hellwig
2006-07-24 22:31 ` David Miller
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=20060708.133738.123994596.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hch@lst.de \
--cc=netdev@vger.kernel.org \
--cc=shemminger@osdl.org \
/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).