xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Daniel Stodden <daniel.stodden@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [RFC PATCH] Xen blkback for 2.6.40.
Date: Mon, 18 Apr 2011 16:12:16 -0400	[thread overview]
Message-ID: <20110418201216.GB12562@dumpdata.com> (raw)
In-Reply-To: <1303151824.9965.72.camel@agari.van.xensource.com>

On Mon, Apr 18, 2011 at 11:37:04AM -0700, Daniel Stodden wrote:
> On Mon, 2011-04-18 at 13:57 -0400, Konrad Rzeszutek Wilk wrote:
> > I am proposing this patch for 2.6.40. This is an RFC at this point.
> > 
> > The git tree for this specific patch is
> > 	git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git devel/xen-blkback-v3.squashed
> > 
> > (the full tree is devel/xen-blkback-v3)
> > 
> > Please take a look at the patch. I know that I need to rewrite the description
> > to have more details for the upstream community - and that will be shortly supplied.
> > 
> > Any thoughts on what I should address/remove/augment/etc would be appreciated. And whether
> > the code has any obvious pitfalls?
> > 
> > The code was originally lifted from 2.6.18, then ported to 2.6.32, and now I have backported
> > it to 2.6.38/.39. scripts/checkpatch.pl had been applied and also some re-ordering of the code
> > has been done to make it easier to read.
> 
> If propose to consider eliminating vbd.c and interface.c, inlining the
> critical bits where they belong, respectively.

Ok. Let me take an axe to that.
> 
> Leaving only blkback.c for the data- and xenbus.c for the control path.

<nods>
> 
> I don't think there's anything notable in there which has more than a
> single position to call it from. It always looked like out of some
> abstraction layer to me, maybe with blktap1 in mind. Beyond that, I
> don't see that getting anywhere.
> 
> Daniel
> 

      reply	other threads:[~2011-04-18 20:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-18 17:57 [RFC PATCH] Xen blkback for 2.6.40 Konrad Rzeszutek Wilk
2011-04-18 17:57 ` [PATCH] xen/blkback: add xen-blkback support Konrad Rzeszutek Wilk
2011-04-18 18:12   ` Konrad Rzeszutek Wilk
2011-04-18 18:31     ` Daniel Stodden
2011-04-18 20:14       ` Konrad Rzeszutek Wilk
2011-04-18 18:37 ` [RFC PATCH] Xen blkback for 2.6.40 Daniel Stodden
2011-04-18 20:12   ` Konrad Rzeszutek Wilk [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=20110418201216.GB12562@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=daniel.stodden@citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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).