From: Jeff Garzik <jgarzik@pobox.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Roman Zippel <zippel@linux-m68k.org>, linux-kernel@vger.kernel.org
Subject: Re: Modules and the Interfaces who Love Them (Take I)
Date: Wed, 13 Nov 2002 23:34:07 -0500 [thread overview]
Message-ID: <3DD327BF.4040705@pobox.com> (raw)
In-Reply-To: <20021114032456.5676D2C0C9@lists.samba.org>
Rusty Russell wrote:
> Slow: Your approach where every interface has to do reference counts
> even though they're only useful for modules makes every interface
> slow, whether they are using modules or not. You can't make them
> fast, because that would make every interface NR_CPUS *
> sizeof(cacheline) larger.
(tangent alert)
Objects controlled by interfaces typically should be ref-counted...
life in the kernel is slowly getting better WRT this, but we're not
there yet. In any case, the ref counts help, not hurt.
Jeff
next prev parent reply other threads:[~2002-11-14 4:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-13 10:17 Modules and the Interfaces who Love Them (Take I) Rusty Russell
2002-11-13 19:02 ` Roman Zippel
2002-11-14 3:34 ` Rusty Russell
2002-11-14 4:34 ` Jeff Garzik [this message]
2002-11-14 10:28 ` Roman Zippel
2002-11-14 11:00 ` Roman Zippel
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=3DD327BF.4040705@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=zippel@linux-m68k.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