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: Wed, 22 Feb 2006 16:06:30 +0100 [thread overview]
Message-ID: <200602221606.30837.carlos@cmartin.tk> (raw)
In-Reply-To: <20060222143604.GA16269@infradead.org>
On Wednesday 22 February 2006 15:36, Christoph Hellwig wrote:
> On Tue, Feb 21, 2006 at 10:03:58PM +0100, Carlos Mart?n wrote:
> > > 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).
>
> even that wouldn't work with current module because the usb and pci modules
> call into the common code and thus we'd have recursive module depency.
And you may not build both modules, so acx-common.ko would never be satisfied.
Function pointers all the way then.
>
> > This approach is probably better even if the driver is unified. Pointer
> > dereferences are cheaper than branches/jumping, aren't they?
>
> It shouldn't matter these days as cpus have nice branch prediction.
I remember reading P4s have problems with this because they had really long
branch pipes (the proper name escapes me at the moment) and if they got it
wrong, it took quite a bit of time (in CPU terms, of course) to flush them. I
don't use them personally, but I believe the trend is to do that.
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
prev parent reply other threads:[~2006-02-22 15:06 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
2006-02-22 14:36 ` Christoph Hellwig
2006-02-22 15:06 ` Carlos Martín [this message]
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=200602221606.30837.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).