linux-um archives
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: Luca Bigliardi <shammash@artha.org>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] [RFC PATCH] vde network backend
Date: Wed, 25 Jul 2007 12:07:00 -0400	[thread overview]
Message-ID: <20070725160700.GA7607@c2.user-mode-linux.org> (raw)
In-Reply-To: <20070725143227.GO5115@pintsize>

On Wed, Jul 25, 2007 at 04:32:27PM +0200, Luca Bigliardi wrote:
> Hi,
> I've written a new network backend for user-mode-linux using libvdeplug to
> connect to a vde_switch. In the following lines I've made a little
> description of what VDE is and I've written a couple of examples to give
> you an idea of the benefits you can have using this backend.
> 
> Please tell me what do you think about vde-transport and its first
> implementation I'm attaching in this mail (It's a patch developed on
> 2.6.22.1 vanilla).

Looks reasonable (and useful).  Do you want me to drop it in my tree
and forward it to mainline?  If so, I'll need a changelog and a
Signed-off-by:.

Some comments -
	style violations :
		there are some cases of return(x) which should be
return x
		if( blah ){ should be if(blah) {
		if(foo) return bar - the return should be on the next
line
		the indentation of multi-line function calls is whacked
	
	I would leave out the likely()s.  Unless you can show a
noticable performance difference, they only clutter the code.
	printks should have severity specified (in userspace code,
they are available as UM_KERN_*)
	um_kmalloc is gone - use kmalloc with UM_GFP_KERNEL

I realize that you probably copied many of the above problems from the
existing code.  All I can say is that I'm gradually fixing them, and
I'd rather not add new instances.

				Jeff	

-- 
Work email - jdike at linux dot intel dot com

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2007-07-25 16:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-25 14:32 [uml-devel] [RFC PATCH] vde network backend Luca Bigliardi
2007-07-25 16:07 ` Jeff Dike [this message]
2007-07-26 17:53   ` Luca Bigliardi
2007-08-12 10:54   ` Blaisorblade
2007-08-12 12:10     ` Luca Bigliardi
2007-08-15 15:20       ` Jeff Dike
2007-08-16  8:47         ` Luca Bigliardi

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=20070725160700.GA7607@c2.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=shammash@artha.org \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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