All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <jbeulich@novell.com>
To: Gerd Hoffmann <kraxel@suse.de>, Keir Fraser <keir@xensource.com>
Cc: Xen devel list <xen-devel@lists.xensource.com>
Subject: Re: Re: [patch/rfc] multiprotocol blkback drivers (32-on-64)
Date: Wed, 20 Dec 2006 15:47:37 +0000	[thread overview]
Message-ID: <45896929.76E4.0078.0@novell.com> (raw)
In-Reply-To: <458952D8.6030803@suse.de>

Looks a lot nicer now, except that I dislike the replication of the request/response
structures in now three places. Besides possibly being a maintenance issue, this
now seems worse in terms of scaling up to eventual future protocol versions. I had
understood Keir in a much different way - adding a compiler abstraction header
(which maybe could even make use of Linux' native ones) to include/xen, and
making use of its abstraction directly in xen/include/public/io/blkif.h.

Jan

>>> Gerd Hoffmann <kraxel@suse.de> 20.12.06 16:12 >>>
Hi,

> I think it would be reasonable to put this stuff in a (new) Linux-specific
> header file that wraps the Xen-public blkif.h. We could put just enough
> support in blkif.h itself to allow it to be multiply-compiled. Then
> different OSes can wrap or rewrite blkif.h as they see fit to get the
> required layout for 32-bit and 64-bit ABIs. This conveniently sidesteps some
> of these issues and allows you to concentrate on Linux and GCC, while not
> constraining the implementation choices for anyone else.

Next interation with exactly that implemented, this time even tested
with blkback in all four combinations out of 32/64 dom0, 32/64 guest.

cheers,
  Gerd

-- 
Gerd Hoffmann <kraxel@suse.de>

  reply	other threads:[~2006-12-20 15:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-18 16:39 [patch/rfc] multiprotocol blkback drivers (32-on-64) Gerd Hoffmann
2006-12-18 17:09 ` Jan Beulich
2006-12-18 17:58   ` Keir Fraser
2006-12-19  7:37     ` Jan Beulich
2006-12-19  8:20   ` Gerd Hoffmann
2006-12-19  7:55 ` Jan Beulich
2006-12-19  8:35   ` Gerd Hoffmann
2006-12-19 13:32   ` Gerd Hoffmann
2006-12-19 14:20     ` Keir Fraser
2006-12-20 15:12       ` Gerd Hoffmann
2006-12-20 15:47         ` Jan Beulich [this message]
2006-12-20 16:07           ` Keir Fraser

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=45896929.76E4.0078.0@novell.com \
    --to=jbeulich@novell.com \
    --cc=keir@xensource.com \
    --cc=kraxel@suse.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.