public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: Greg KH <greg@kroah.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	"Van De Ven, Arjan" <arjan@linux.intel.com>,
	Al Viro <viro@ZenIV.linux.org.uk>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Fixing the main programmer thinko with the device model
Date: Wed, 26 Mar 2008 06:07:49 +0100	[thread overview]
Message-ID: <1206508069.24783.16.camel@lov.site> (raw)
In-Reply-To: <20080326041631.GB28224@kroah.com>

On Tue, 2008-03-25 at 21:16 -0700, Greg KH wrote:
> On Tue, Mar 25, 2008 at 10:57:32AM +0100, Andi Kleen wrote:
> > James Bottomley <James.Bottomley@HansenPartnership.com> writes:
> > > 
> > > That's true, but irrelevant (and also soon to be untrue if we get rid of
> > > the scsi_device class as you and Kay keep requesting).  The two calls
> > > release references on the actual embedded generic device, it's nothing
> > > to do with entangled lifetime rules.
> > 
> > <heretic thought>Has anybody ever considered just doing away with 
> > the problematic and bug prone and tricky reference counts for kobjects 
> > and switch to a simple garbage collector for them?
> 
> Sure, I have no objection to that.  It's just that the reference count
> "issue" really doesn't seem to be one on sanely designed busses :)

Hmm, what is a "simple garbage collector" here? How could one determine
"reachability" of objects, means: at what point of time do objects
actually become "garbage"? How could one trace in our current kernel
code who still accesses an object, without doing refcounts?

Kay


  reply	other threads:[~2008-03-26  5:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-24 15:39 Fixing the main programmer thinko with the device model James Bottomley
2008-03-24 17:58 ` Greg KH
2008-03-24 18:08   ` James Bottomley
2008-03-25  9:57     ` Andi Kleen
2008-03-26  4:16       ` Greg KH
2008-03-26  5:07         ` Kay Sievers [this message]
2008-03-26  5:23           ` Greg KH

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=1206508069.24783.16.camel@lov.site \
    --to=kay.sievers@vrfy.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=andi@firstfloor.org \
    --cc=arjan@linux.intel.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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