[Xen-devel] [RFC 21/23] net/xen-netback: Make it running on 64KB page granularity
From: Wei Liu <hidden>
Date: 2015-05-18 12:54:19
Also in:
lkml, netdev
On Mon, May 18, 2015 at 01:11:26PM +0100, Julien Grall wrote:
Hi Wei, On 15/05/15 16:31, Wei Liu wrote:quoted
On Fri, May 15, 2015 at 01:35:42PM +0100, Julien Grall wrote:quoted
On 15/05/15 03:35, Wei Liu wrote:quoted
On Thu, May 14, 2015 at 06:01:01PM +0100, Julien Grall wrote:quoted
The PV network protocol is using 4KB page granularity. The goal of this patch is to allow a Linux using 64KB page granularity working as a network backend on a non-modified Xen. It's only necessary to adapt the ring size and break skb data in small chunk of 4KB. The rest of the code is relying on the grant table code. Although only simple workload is working (dhcp request, ping). If I try to use wget in the guest, it will stall until a tcpdump is started on the vif interface in DOM0. I wasn't able to find why.I think in wget workload you're more likely to break down 64K pages to 4K pages. Some of your calculation of mfn, offset might be wrong.If so, why tcpdump on the vif interface would make wget suddenly working? Does it make netback use a different path?No, but if might make core network component behave differently, this is only my suspicion. Do you see malformed packets with tcpdump?I don't see any malformed packets with tcpdump. The connection is stalling until tcpdump is started on the vif in dom0.
Hmm... Don't have immediate idea about this. Ian said skb_orphan is called with tcpdump. If I remember correct that would trigger the callback to release the slots in netback. It could be that other part of Linux is holding onto the skbs for too long. If you're wgetting from another host, I would suggest wgetting from Dom0 to limit the problem between Dom0 and DomU.
quoted hunk ↗ jump to hunk
quoted
quoted
quoted
quoted
I have not modified XEN_NETBK_RX_SLOTS_MAX because I wasn't sure what it's used for (I have limited knowledge on the network driver).This is the maximum slots a guest packet can use. AIUI the protocol still works on 4K granularity (you break 64K page to a bunch of 4K pages), you don't need to change this.1 slot = 1 grant right? If so, XEN_NETBK_RX_SLOTS_MAX is based on the number of Linux page. So we would have to get the number for Xen page.Yes, 1 slot = 1 grant. I see what you're up to now. Yes, you need to change this constant to match underlying HV page.quoted
Although, I gave a try to multiple by XEN_PFN_PER_PAGE (4KB/64KB = 16) but it get stuck in the loop.I don't follow. What is the new #define? Which loop does it get stuck?diff --git a/drivers/net/xen-netback/common.h b/drivers/net/xen-netback/common.h index 0eda6e9..c2a5402 100644 --- a/drivers/net/xen-netback/common.h +++ b/drivers/net/xen-netback/common.h@@ -204,7 +204,7 @@ struct xenvif_queue { /* Per-queue data for xenvif */ /* Maximum number of Rx slots a to-guest packet may use, including the * slot needed for GSO meta-data. */ -#define XEN_NETBK_RX_SLOTS_MAX (MAX_SKB_FRAGS + 1) +#define XEN_NETBK_RX_SLOTS_MAX ((MAX_SKB_FRAGS + 1) * XEN_PFN_PER_PAGE) enum state_bit_shift { /* This bit marks that the vif is connected */The function xenvif_wait_for_rx_work never returns. I guess it's because there is not enough slot available. For 64KB page granularity we ask for 16 times more slots than 4KB page granularity. Although, it's very unlikely that all the slot will be used. FWIW I pointed out the same problem on blkfront.
This is not going to work. The ring in netfront / netback has only 256 slots. Now you ask for netback to reserve more than 256 slots -- (17 + 1) * (64 / 4) = 288, which can never be fulfilled. See the call to xenvif_rx_ring_slots_available. I think XEN_NETBK_RX_SLOTS_MAX derived from the fact the each packet to the guest cannot be larger than 64K. So you might be able to #define XEN_NETBK_RX_SLOTS_MAX ((65536 / XEN_PAGE_SIZE) + 1) Blk driver may have a different story. But the default ring size (1 page) yields even less slots than net (given that sizeof(union(req/rsp)) is larger IIRC). Wei.