From: "Carlos Martín" <carlos@cmartin.tk>
To: Christoph Hellwig <hch@infradead.org>
Cc: netdev@vger.kernel.org, acx100-devel@lists.sourceforge.net
Subject: Re: From: Carlos Mart??n <carlos@cmartin.tk>
Date: Tue, 21 Feb 2006 22:03:58 +0100 [thread overview]
Message-ID: <200602212203.58216.carlos@cmartin.tk> (raw)
In-Reply-To: <20060221203211.GA29627@infradead.org>
On Tuesday 21 February 2006 21:32, Christoph Hellwig wrote:
> On Tue, Feb 21, 2006 at 09:24:23PM +0100, Carlos Mart?n wrote:
> > Wouldn't this lead to duplicated function definitions at link time if both
are
> > compiled-in? From your module split above I understood you wanted
acx-common
> > to be another module, but here I see it goes into the modules.
> >
>
> No. The above makefile fragment builds three modules: acx-common.o,
> acx-pci.o and acx-usb.o as mentioned above. The magic here is that with
> that makefile fragment is that the kbuild systems builds acx-common.o if
> either CONFIG_ACX_PCI or CONFIG_ACX_USB is set, and even makes sure to
> do the right thing if either is builtin. There is not code duplication
> at all.
Then all is good.
>
> > > ---- snip ----
> > >
> > > - kill the IS_PCI/IS_USB macros and add a acx_operations structure that
> > > handles the different hardware without branches all over and allows
> > > the hw-specific code to be in separate modules.
> >
> > There aren't that many IS_{PCI,USB} uses and most if not all are justified
> > (extra step for one case). It might be a good idea to do that for the
> > IS_ACX{100,111} macros instead of calling the generic function which then
> > calls the chip-specific one.
>
> The important bit is that you need the pointers with the above module
> spit, because you can't call usb- or pci-specific routines from
> acx-common.ko
Yes, I realise that (unless you export them, but I don't think we want that).
I've started this, but I think it'll probably be next week before I have time
to really work on it.
This approach is probably better even if the driver is unified. Pointer
dereferences are cheaper than branches/jumping, aren't they?
cmn
--
Carlos Martín Nieto | http://www.cmartin.tk
Hobbyist programmer |
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&dat\x121642
next prev parent reply other threads:[~2006-02-21 21:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-18 22:35 From: Carlos Martín <carlos@cmartin.tk> Carlos Martin
2006-02-18 22:38 ` From: Carlos MartÃn <carlos@cmartin.tk> Carlos Martín
2006-02-20 15:30 ` From: Carlos Martц╜n <carlos@cmartin.tk> Denis Vlasenko
2006-02-20 18:56 ` Carlos Martín
2006-02-21 6:17 ` Denis Vlasenko
2006-02-21 14:31 ` Carlos Martín
2006-02-21 19:26 ` From: Carlos Mart??n <carlos@cmartin.tk> Christoph Hellwig
2006-02-21 20:24 ` Carlos Martín
2006-02-21 20:32 ` Christoph Hellwig
2006-02-21 21:03 ` Carlos Martín [this message]
2006-02-22 14:36 ` Christoph Hellwig
2006-02-22 15:06 ` Carlos Martín
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=200602212203.58216.carlos@cmartin.tk \
--to=carlos@cmartin.tk \
--cc=acx100-devel@lists.sourceforge.net \
--cc=hch@infradead.org \
--cc=netdev@vger.kernel.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).