All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: annie li <annie.li@oracle.com>
Cc: "Roger Pau Monné" <roger.pau@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Rebooting domu fails in nfs share exported from another domu on the same dom0
Date: Fri, 18 Jul 2014 15:43:34 -0400	[thread overview]
Message-ID: <20140718194334.GK15947@laptop.dumpdata.com> (raw)
In-Reply-To: <53C9761F.3040803@oracle.com>

On Fri, Jul 18, 2014 at 03:31:43PM -0400, annie li wrote:
> 
> On 2014/7/18 14:53, Konrad Rzeszutek Wilk wrote:
> >On Thu, Jul 17, 2014 at 12:56:12PM -0400, annie li wrote:
> >>On 2014/7/17 11:49, Roger Pau Monné wrote:
> >>>On 16/07/14 22:36, annie li wrote:
> >>>>Hi
> >>>>
> >>>>I hit a problem in such scenario: vm1 is running and export nfs service,
> >>>>dom0 mount this nfs, and vm2 is booted in this nfs location. vm1 and vm2
> >>>>are running on the same dom0.
> >>>>
> >>>>When this bug happens, the data flow is:  vm2 blkfront-> vm2 blkback->
> >I am a bit confused here. 'vm2 blkfront -> vm2 blkback'? Did you
> >mean 'dom0 blkback'?
> 
> Yes, Dom0 blkback.
> 
> >
> >
> >>>>loop -> nfs file -> nfs client -> bridge priv1 -> vm1 vif -> vm1 netback
> >>>>-> vm1 netfront.
> >So both netback and netfront run in the same guest? I think you
> >want these two swapped around (netfront -> netback).
> 
> No, the netfront in above routine means the one in guest vm1, and this is
> network RX path in vm1.

OK, so 'dom0 netback' then. As the netback thread is running in the
initial domain?

So a revised view is:

  vm2 blkfront -> dom0 blkback -> loop -> nfs file -> nfs client
	-> bridge priv1 -> vm1 vif -> dom0 netback -> vm1 netfront

So with the grant map (blkfront -> blkback) the source is dom0
and the destination is vm1. For the grant copy, the source is
dom0 and the destinatation is vm2 right? (or did I get my src
and dst confused?).

  reply	other threads:[~2014-07-18 19:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-16 20:36 Rebooting domu fails in nfs share exported from another domu on the same dom0 annie li
2014-07-17 15:49 ` Roger Pau Monné
2014-07-17 16:56   ` annie li
2014-07-18 18:53     ` Konrad Rzeszutek Wilk
2014-07-18 19:31       ` annie li
2014-07-18 19:43         ` Konrad Rzeszutek Wilk [this message]
2014-07-18 20:17           ` annie li
2014-07-18 20:22             ` Konrad Rzeszutek Wilk
2014-07-18 20:31               ` annie li
2014-07-18 21:07                 ` Konrad Rzeszutek Wilk
2014-07-18 21:43                   ` annie li
2014-07-21 10:02                     ` Wei Liu
2014-07-21 15:02                       ` annie li
2014-07-21 23:05                         ` Wei Liu
2014-07-23  1:58                           ` annie li
2014-07-28 14:14 ` David Vrabel
2014-07-28 16:14   ` annie li

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=20140718194334.GK15947@laptop.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=annie.li@oracle.com \
    --cc=roger.pau@citrix.com \
    --cc=xen-devel@lists.xen.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 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.