netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: arnaldo.melo@gmail.com
Cc: jmorris@namei.org, netdev@vger.kernel.org, dccp@vger.kernel.org
Subject: Re: [PATCH] dccp: remove module exit functions
Date: Mon, 13 Nov 2006 16:49:09 -0800 (PST)	[thread overview]
Message-ID: <20061113.164909.35016870.davem@davemloft.net> (raw)
In-Reply-To: <39e6f6c70611101032v5f0be644ta65069cf533b3385@mail.gmail.com>

From: "Arnaldo Carvalho de Melo" <arnaldo.melo@gmail.com>
Date: Fri, 10 Nov 2006 16:32:16 -0200

> On 11/10/06, James Morris <jmorris@namei.org> wrote:
> > On Fri, 10 Nov 2006, James Morris wrote:
> >
> > > I wonder if this facility can be integrated more generally into the kernel
> > > protocol which people are developing.
> >
> > Ugh, editor screwup.  That was meant to be
> >
> > I wonder if this facility can be integrated more generally into the kernel
> > as a kernel hacking option, as this is not the only protocol which people
> > are developing.
> >
> 
> See:
> http://www.erg.abdn.ac.uk/users/gerrit/dccp/patch-backlog/09a_release_ctl_socket_at_exit.diff
> 
> This one requires a bit more thinking, so I'm postponing it for now to
> get the simple bits in Gerrit's patch queue cherrypicked and sent for
> Dave.

One possible way to handle this is to flag certain sockets such that
no refrence counting is done for them against the module.  It is
an indication that the module will take care of such sockets on
cleanup.

It seems that this would limit the cost to a test at socket create
and destroy time.

  parent reply	other threads:[~2006-11-14  0:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-10  8:48 [PATCH] dccp: remove module exit functions James Morris
2006-11-10 13:55 ` Arnaldo Carvalho de Melo
2006-11-10 16:24   ` James Morris
2006-11-10 16:27     ` James Morris
2006-11-10 18:32       ` Arnaldo Carvalho de Melo
2006-11-13 13:41         ` Gerrit Renker
2006-11-14  0:49         ` David Miller [this message]
2006-11-14 14:11           ` Arnaldo Carvalho de Melo

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=20061113.164909.35016870.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=arnaldo.melo@gmail.com \
    --cc=dccp@vger.kernel.org \
    --cc=jmorris@namei.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).