[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] RFC: [0/2] Remove netloop by lazy copying in netback


  • To: Keir Fraser <keir@xxxxxxxxxxxxx>, Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>, Xen Development Mailing List <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxxxxxxxx>
  • Date: Tue, 20 Mar 2007 10:27:48 +0000
  • Delivery-date: Tue, 20 Mar 2007 03:26:57 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acdq2aJ+4UeWBdbMEduzOgAX8io7RQAAMVLU
  • Thread-topic: [Xen-devel] RFC: [0/2] Remove netloop by lazy copying in netback



On 20/3/07 10:22, "Keir Fraser" <keir@xxxxxxxxxxxxx> wrote:

> One other thought I had -- does the Linux network stack ever modify date
> residing outside the main skbuff data area (i.e., data in fragments)? If it
> ever does, wouldn't your delayed copy in netback potentially race such
> updates? If the Linux network stack guarantees never to do such a thing,
> that would be nice for us. :-)

Scrub that question: we already map the grants read-only, so the network
stack can't be trying to write to fragments.

 -- Keir


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.