public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Addison <addy@quadrics.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Brice Goglin <Brice.Goglin@ens-lyon.org>,
	Andrew Morton <akpm@osdl.org>, Andrea Arcangeli <andrea@suse.de>,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][RFC] Linux VM hooks for advanced RDMA NICs
Date: Fri, 29 Apr 2005 10:25:47 +0100	[thread overview]
Message-ID: <4271FD9B.8000402@quadrics.com> (raw)
In-Reply-To: <1114762772.7183.285.camel@gaston>



Benjamin Herrenschmidt wrote:
>>>+ioproc_register_ops(struct mm_struct *mm, struct ioproc_ops *ip)
>>>+{
>>>+	ip->next = mm->ioproc_ops;
>>>+	mm->ioproc_ops = ip;
>>>+
>>>+	return 0;
>>>+}
>>>+
> 
> Why not use a list_head along with linux standard list primitives ?
> 
> Ben.
> 
> 
The reason we didn't use the standard list primitives was that we wanted the normal
case where no ioproc ops were registered to have minimal impact and this just comes
down to mm->ioproc_ops being checked against being zero, which is slightly lighter weight
than using the list primitives.

Also entries are rarely removed from the list using the ioproc_deregister function as
in the normal case they get removed in the call to ioproc_release.  Hence there is little
need for the doubly linked list.

Cheers,
David
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

      reply	other threads:[~2005-04-29  9:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-26 15:49 [PATCH][RFC] Linux VM hooks for advanced RDMA NICs David Addison
2005-04-26 16:57 ` Jesper Juhl
2005-04-26 17:13   ` Lee Revell
2005-04-26 17:20     ` Jesper Juhl
2005-04-26 17:28       ` Lee Revell
2005-04-26 17:38         ` Jesper Juhl
2005-04-26 20:14         ` John W. Linville
2005-04-26 20:17           ` Lee Revell
2005-04-26 20:09       ` Lars Marowsky-Bree
2005-04-28 11:34     ` Jakob Oestergaard
2005-04-29  8:22     ` Benjamin Herrenschmidt
2005-04-26 17:06 ` Brice Goglin
2005-04-27  9:41   ` David Addison
2005-04-28  8:38     ` Andy Isaacson
2005-04-27 13:43   ` Andi Kleen
2005-04-28  1:42 ` Troy Benjegerdes
2005-04-28  7:21 ` Brice Goglin
2005-04-28  9:21   ` David Addison
2005-04-29  8:19   ` Benjamin Herrenschmidt
2005-04-29  9:25     ` David Addison [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=4271FD9B.8000402@quadrics.com \
    --to=addy@quadrics.com \
    --cc=Brice.Goglin@ens-lyon.org \
    --cc=akpm@osdl.org \
    --cc=andrea@suse.de \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@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