mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BK PATCH] devfs cleanups for 2.5.29
Date: Tue, 20 Aug 2002 22:01:00 -0600	[thread overview]
Message-ID: <200208210401.g7L410F21464@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <Pine.LNX.4.44.0208201923470.28515-100000@serv>

Roman Zippel writes:
> Hi,
> 
> On Tue, 20 Aug 2002, Richard Gooch wrote:
> 
> > > So where again is the module count
> > > incremented?
> >
> > Which kernel tree are you looking at? I'm looking at 2.4.20-pre4.
> 
> Try 2.5.x.

Ah, that explains why we seemed to be talking past each other. For
2.4.x, def_blk_fops.open() will bump the reference count, but in 2.5.x
it won't. So in 2.5.x, fs/devfs/base.c:devfs_open() shouldn't drop the
refcount after def_blk_fops.open() returns.

> > > You never answered my question, why you insist on managing the ops
> > > pointer. The far easier fix would be to simply remove this nonsense.
> >
> > Because it's an optimsation, avoiding the need for looking up ops from
> > tables/lists. It's the sensible way of doing it. I've explained this
> > to others on the list, and in the FAQ. I'm not going to keep going
> > over it again and again.
> 
> Optimization??? This would require any device had to be be opened
> _only_ through devfs, you are not seriously suggesting that???

Huh? Of course not! All I'm saying is that if you use devfs, the
optimisation will short-circuit the lookups.

				Regards,

					Richard....
Permanent: rgooch@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca

  reply	other threads:[~2002-08-21  3:56 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-30 22:54 Greg KH
2002-07-30 22:54 ` Greg KH
2002-07-30 22:55   ` Greg KH
2002-07-30 23:12 ` Richard Gooch
2002-07-30 23:18   ` Greg KH
2002-07-30 23:46     ` Greg KH
2002-07-30 23:35   ` Roman Zippel
2002-07-30 23:41     ` Richard Gooch
2002-07-31  0:31       ` Roman Zippel
2002-07-31  0:32         ` Richard Gooch
2002-07-31  9:32           ` Roman Zippel
2002-08-05 22:12             ` Richard Gooch
2002-08-05 22:48               ` Roman Zippel
2002-08-19  0:48                 ` Richard Gooch
2002-08-19  9:37                   ` Roman Zippel
2002-08-20 17:00                     ` Richard Gooch
2002-08-20 17:29                       ` Roman Zippel
2002-08-21  4:01                         ` Richard Gooch [this message]
2002-08-21 11:22                           ` Roman Zippel
2002-07-31 20:30 ` Marcin Dalecki
2002-08-01  9:57   ` Jens Axboe

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=200208210401.g7L410F21464@vindaloo.ras.ucalgary.ca \
    --to=rgooch@ras.ucalgary.ca \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®