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

Re: [Xen-devel] pcnet32 and copybreak condition

> The main modifications in the PCnet32 ethernet driver seems to be macro that
> test if COPYBREAK is define. I notice that for network driver which were 
> written
> for Xen the main modifications was around the copybreak and also some
> adjustments with include files. Is it true if I say that the port of network
> device from Linux to Xen is quite "easy" and that the majority of the
> modifications are due to the differences with inlcude files and differences 
> with
> "copybreak" scheme? 

Porting network drivers is usually straight forward. 

We could add a few more dummy header files to make the job even
easier, but since we're planning on moving to a new IO scheme we
haven't put much effort into this.

Areas of memory into which packets are received are not by
default mapped into Xen's virtual address space, hence using the
CPU to memcpy the data (as in COPYBREAK) doesn't work unless you
add a 'map_domain_mem' call in front of it. The quick and easy
fix in the case of pcnet32 was just to disable COPYBREAK.

> You plan to move the management of device in domain0 using the native linux
> device drivers right? Have you ever write something concerning what are the
> differents steps that will allow to achieve this goal? 

I'm in the process of writing a document that describes the Xen
road map, and will post it to the list.


This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
Xen-devel mailing list



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