virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: tgh <wwwwww4187@sina.com.cn>
To: Mark Williamson <mark.williamson@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com,
	'Eduardo Habkost' <ehabkost@redhat.com>,
	'Juan Quintela' <quintela@redhat.com>,
	"'Stephen C. Tweedie'" <sct@redhat.com>,
	'Jan Beulich' <jbeulich@novell.com>,
	'Glauber de Oliveira Costa' <gcosta@redhat.com>,
	'Chris Wright' <chrisw@sous-sol.org>,
	virtualization@lists.osdl.org, dgm36@cam.ac.uk,
	'Gerd Hoffmann' <kraxel@redhat.com>
Subject: Re: Re: Next steps with pv_ops for Xen
Date: Tue, 04 Dec 2007 17:35:44 +0800	[thread overview]
Message-ID: <47551F70.7080300@sina.com.cn> (raw)
In-Reply-To: <200712031908.11079.mark.williamson@cl.cam.ac.uk>

hi
I am not quite clear about the purpose of pv-ops , what do we want to 
deal with by developping "pv-ops"? is it used for HVM or for PV or KVM 
or something ? I have seen it for a few months in the list ,and 
"pv-ops"is an active project ,but i am not clear about what is the aim 
of "pv-ops" ,could you give me an explanation about it

Thanks in advance




Mark Williamson 写道:
>> Hi Mark,
>>
>>     
>>> Maybe a change to the gntdev userspace API to allow batching
>>> of mapping requests?
>>>       
>> Something along the lines of the following?
>>     
>
> Just like that :-D
>
> When you said "multiple syscalls per mapping" I assumed you meant that we'd 
> lose the batching you get by doing a mulicall.  If it's just a couple of 
> syscalls (plus, presumably a couple of hypercalls) per batch of mappings, my 
> gut says it's probably not going to hurt block performance.  My guts have 
> been wrong in (many!) ways before of course...
>
> I guess the overhead *could* be reduced even more by just having a magic ioctl 
> that did all the mmap-ing stuff in one operation, but that'd probably be 
> really gross if it wasn't necessary!  And I doubt it'd make upstream very 
> happy...
>
> We'll also be eliminating the overheads involved in having a blktap ring for 
> talking to userspace and having to move requests between that ring and the 
> real block ring, so there's some definite wins in overheads as well.
>
> Cheers,
> Mark
>
>   

  reply	other threads:[~2007-12-04  9:35 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-21 22:05 Next steps with pv_ops for Xen Stephen C. Tweedie
2007-11-21 23:12 ` Jeremy Fitzhardinge
2007-11-26 14:02   ` Juan Quintela
2007-11-26 18:52     ` Jeremy Fitzhardinge
2007-11-27  8:30       ` Jan Beulich
2007-11-27 17:00         ` Jeremy Fitzhardinge
2007-11-27 17:14           ` Jan Beulich
2007-11-27 17:15           ` Stephen C. Tweedie
2007-12-03 12:54 ` Gerd Hoffmann
2007-12-03 13:19   ` Derek Murray
2007-12-03 14:16     ` Gerd Hoffmann
2007-12-03 14:51       ` Derek Murray
2007-12-03 17:18         ` Mark Williamson
2007-12-03 18:36           ` D.G. Murray
2007-12-03 19:08             ` Mark Williamson
2007-12-04  9:35               ` tgh [this message]
2007-12-05  3:42                 ` Mark Williamson
2007-12-06 15:21             ` Gerd Hoffmann
2007-12-06 15:32               ` Derek Murray
2007-12-06 15:55                 ` Gerd Hoffmann
2007-12-21 12:58             ` [Xen-devel] " Gerd Hoffmann
2007-12-03 20:38         ` Gerd Hoffmann
2007-12-04  9:40           ` Derek Murray
2007-12-04 12:01             ` Gerd Hoffmann
2007-12-04 12:39               ` Stephen C. Tweedie
2007-12-04 19:58                 ` Gerd Hoffmann
2007-12-05 11:48                   ` [Xen-devel] " Derek Murray
2007-12-05 13:19                   ` Derek Murray
     [not found]                   ` <47569014.8080008@cl.cam.ac.uk>
2007-12-05 14:12                     ` Gerd Hoffmann
2007-12-05 14:22                       ` Keir Fraser
2007-12-05 14:30                         ` Derek Murray
2007-12-05 16:58                           ` Keir Fraser
2007-12-05 17:17                             ` Derek Murray
2007-12-05 17:22                               ` Keir Fraser
2007-12-05 17:48                                 ` Derek Murray
2007-12-05 17:59                                   ` Keir Fraser
2007-12-05 18:15                                     ` Derek Murray
2007-12-12  8:27                                       ` Isaku Yamahata
2007-12-12  8:39                                         ` Keir Fraser
2007-12-12  8:44                                           ` Isaku Yamahata
2007-12-05 20:06                                     ` Gerd Hoffmann
2007-12-05 18:12                     ` Jeremy Fitzhardinge
2007-12-05 18:29                       ` Derek Murray
2007-12-05 20:15                         ` Jeremy Fitzhardinge
2007-12-05 20:35                           ` Geoffrey Lefebvre
2007-12-06 10:15                             ` Gerd Hoffmann
2007-12-05 20:44                           ` Keir Fraser
2007-12-06 10:00                             ` Derek Murray
2007-12-06 19:55                               ` [Xen-devel] " Jeremy Fitzhardinge
2007-12-05 10:03                 ` Gerd Hoffmann
2007-12-05 12:51                   ` Gerd Hoffmann
2007-12-05 10:11                 ` Derek Murray

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=47551F70.7080300@sina.com.cn \
    --to=wwwwww4187@sina.com.cn \
    --cc=chrisw@sous-sol.org \
    --cc=dgm36@cam.ac.uk \
    --cc=ehabkost@redhat.com \
    --cc=gcosta@redhat.com \
    --cc=jbeulich@novell.com \
    --cc=kraxel@redhat.com \
    --cc=mark.williamson@cl.cam.ac.uk \
    --cc=quintela@redhat.com \
    --cc=sct@redhat.com \
    --cc=virtualization@lists.osdl.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 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).