All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xensource.com>
To: Tracy R Reed <treed@ultraviolet.org>, xen-devel@lists.xensource.com
Subject: Re: Xen/AoE skb frag array incompatibility
Date: Fri, 08 Dec 2006 06:27:30 +0000	[thread overview]
Message-ID: <C19EB652.5869%keir@xensource.com> (raw)
In-Reply-To: <4578C732.1020206@ultraviolet.org>

Is there a clear technical description of what the problem is? I see three
problems vaguely referred to in this email:
 1. Build failure on skb_linearize()
 2. Warnings about 'can't schedule work'
 3. Some unspecified problem with frag lists

If someone digs into the problem a bit and points us at some code we can
probably advise what should be done.

 -- Keir

On 8/12/06 2:00 am, "Tracy R Reed" <treed@ultraviolet.org> wrote:

> Greetings, Xen developers!
> 
> I have been using AoE with Xen to great effect and I am very pleased
> with how the whole system has worked out. The two technologies really
> complement each other. I consider it the ultimate setup. Aside from the
> network switch (eventually to be remedied) my serving infrastructure has
> zero single points of failure.
> 
> However, this virtualization paradise has a flaw: There seems to be some
> sort of incompatibility in the way AoE uses the skb frag array in the
> latest version of AoE (6-40) and in the way Xen uses it. This causes new
> AoE block devices to fail to be accessible among potentially other problems.
> 
> Is anyone aware of this problem? It is not clear to me if it is a
> problem with Xen or if the fault lies in AoE. I have looked into it a
> bit but my kernel hacking talents are rather meager. Attached is a
> recent email from the AoE list discussing it. If you have any
> suggestions for the AoE folks they can be reached over at
> aoetools-discuss@lists.sourceforge.net

      reply	other threads:[~2006-12-08  6:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-08  2:00 Xen/AoE skb frag array incompatibility Tracy R Reed
2006-12-08  6:27 ` Keir Fraser [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=C19EB652.5869%keir@xensource.com \
    --to=keir@xensource.com \
    --cc=treed@ultraviolet.org \
    --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.