netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Evgeniy Polyakov <zbr@ioremap.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: device-mapper development <dm-devel@redhat.com>,
	netdev@vger.kernel.org, Jonathan Brassow <jbrassow@redhat.com>
Subject: Re: [dm-devel] Updated cluster log patch (take 5)
Date: Mon, 6 Jul 2009 16:19:02 +0400	[thread overview]
Message-ID: <20090706121902.GA5660@ioremap.net> (raw)
In-Reply-To: <20090706114217.GA1679@infradead.org>

On Mon, Jul 06, 2009 at 07:42:17AM -0400, Christoph Hellwig (hch@infradead.org) wrote:
> On Sat, Jun 20, 2009 at 08:01:29AM -0400, Thomas Graf wrote:
> > > Maye I misremember it, but isn't the connector code strongly deprecated
> > > in favour of genetlink?
> > 
> > Use of connector is deprecated, it does not have any advantages over
> > genetlink while genetlink provides an optional attributes based
> > protocol interface which allows for messaging protocols to be developed
> > which can be extended without breaking binary compatibility. It also
> > features a userspace library which makes development trivial.
> > 
> > 
> > I guess nobody will force you but use of genetlink is encouraged.
> 
> Jonathan, I think it's really sad that this got pushed into mainline
> after the merge window without even replying to this statement of one
> of our core networking developers.

Apparently Christoph never tried neither connector nor genetlink.
Because the former has very different interface than the latter.
Genetlink was created for network developers who are familiar with
attribute lists (used long before both were created), skbs and inner
structure of the received packet. While connector has interface with a
single purpose of being a simple callback invocation for those who do
not want to dig into network land to get a message from the userspace.

As of talking about advantages of the inner structure of how both
operate please check the code, there is a fair number of things one can
do with one and another systems.

-- 
	Evgeniy Polyakov

      reply	other threads:[~2009-07-06 12:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1244845317.19994.3.camel@hydrogen.msp.redhat.com>
2009-06-13 11:07 ` [dm-devel] Updated cluster log patch (take 5) Christoph Hellwig
2009-06-14 16:24   ` Evgeniy Polyakov
2009-06-20 12:01   ` Thomas Graf
2009-07-06 11:42     ` Christoph Hellwig
2009-07-06 12:19       ` Evgeniy Polyakov [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=20090706121902.GA5660@ioremap.net \
    --to=zbr@ioremap.net \
    --cc=dm-devel@redhat.com \
    --cc=hch@infradead.org \
    --cc=jbrassow@redhat.com \
    --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).