netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Evgeniy Polyakov <zbr@ioremap.net>
To: Gleb Natapov <gleb@redhat.com>
Cc: Anthony Liguori <anthony@codemonkey.ws>,
	David Miller <davem@davemloft.net>,
	netdev@vger.kernel.org,
	virtualization@lists.linux-foundation.org, kvm@vger.kernel.org
Subject: Re: [PATCH] AF_VMCHANNEL address family for guest<->host communication.
Date: Wed, 17 Dec 2008 00:25:32 +0300	[thread overview]
Message-ID: <20081216212532.GA15360@ioremap.net> (raw)
In-Reply-To: <20081216065727.GD13794@redhat.com>

On Tue, Dec 16, 2008 at 08:57:27AM +0200, Gleb Natapov (gleb@redhat.com) wrote:
> > Another approach is to implement that virtio backend with netlink based
> > userspace interface (like using connector or genetlink). This does not
> > differ too much from what you have with special socket family, but at
> > least it does not duplicate existing functionality of
> > userspace-kernelspace communications.
> > 
> I implemented vmchannel using connector initially (the downside is that
> message can be dropped). Is this more expectable for upstream? The
> implementation was 300 lines of code.

Hard to tell, it depends on implementation. But if things are good, I
have no objections as connector maintainer :)

Messages in connector in particular and netlink in general are only
dropped, when receiving buffer is full (or when there is no memory), you
can tune buffer size to match virtual queue size or vice versa.

-- 
	Evgeniy Polyakov

  reply	other threads:[~2008-12-16 21:25 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-14 11:50 [PATCH] AF_VMCHANNEL address family for guest<->host communication Gleb Natapov
2008-12-14 12:23 ` Evgeniy Polyakov
2008-12-14 12:46   ` Gleb Natapov
2008-12-15  6:44 ` David Miller
2008-12-15  7:48   ` Gleb Natapov
2008-12-15  8:27     ` David Miller
2008-12-15 15:02   ` Anthony Liguori
2008-12-15 17:45     ` Jeremy Fitzhardinge
2008-12-15 18:26       ` Itamar Heim
2008-12-15 18:45       ` Anthony Liguori
2008-12-15 22:52         ` Jeremy Fitzhardinge
2008-12-15 23:08           ` Anthony Liguori
2008-12-15 23:44             ` Jeremy Fitzhardinge
2008-12-15 23:52             ` Evgeniy Polyakov
2008-12-16  0:01               ` Dor Laor
2008-12-15 19:43     ` David Miller
2008-12-15 20:44       ` Anthony Liguori
2008-12-15 22:29         ` David Miller
2008-12-15 23:01           ` Anthony Liguori
2008-12-15 23:10             ` David Miller
2008-12-15 23:17               ` Anthony Liguori
2008-12-16  2:55                 ` Herbert Xu
2008-12-15 23:13             ` Stephen Hemminger
2008-12-15 23:45             ` Evgeniy Polyakov
2008-12-16  6:57               ` Gleb Natapov
2008-12-16 21:25                 ` Evgeniy Polyakov [this message]
2008-12-16 23:20                   ` Dor Laor
2008-12-17 14:31                   ` Gleb Natapov
2008-12-18 12:30                     ` Evgeniy Polyakov

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=20081216212532.GA15360@ioremap.net \
    --to=zbr@ioremap.net \
    --cc=anthony@codemonkey.ws \
    --cc=davem@davemloft.net \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.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).