Displaying 20 results from an estimated 600 matches similar to: "Dom0 physical networking/swiotlb/something issue in 3.7-rc1"
2007 Jun 11
5
[PATCH][Linux] gnttab: make dma address conversion logic of gnttab dma arch specific.
This patch is cleaned up of the patch which was sent as
http://lists.xensource.com/archives/html/xen-devel/2007-06/msg00324.html
# HG changeset patch
# User yamahata@valinux.co.jp
# Date 1181545986 -32400
# Node ID 69e2dd4e06c405a92717c5f1818f5096e1dc0bcd
# Parent d5e0eb7dd069c0ffc1854da81aa143ccfb0ad66e
make dma address conversion logic of gnttab dma arch specific.
gnttab_dma_map_page() and
2014 Nov 24
2
[PATCH v3 04/41] virtio: memory access APIs
On Mon, Nov 24, 2014 at 01:03:24PM +0100, Geert Uytterhoeven wrote:
> On Mon, Nov 24, 2014 at 12:52 PM, Michael S. Tsirkin <mst at redhat.com> wrote:
> > virtio 1.0 makes all memory structures LE, so
> > we need APIs to conditionally do a byteswap on BE
> > architectures.
> >
> > To make it easier to check code statically,
> > add virtio specific types
2014 Nov 24
2
[PATCH v3 04/41] virtio: memory access APIs
On Mon, Nov 24, 2014 at 01:03:24PM +0100, Geert Uytterhoeven wrote:
> On Mon, Nov 24, 2014 at 12:52 PM, Michael S. Tsirkin <mst at redhat.com> wrote:
> > virtio 1.0 makes all memory structures LE, so
> > we need APIs to conditionally do a byteswap on BE
> > architectures.
> >
> > To make it easier to check code statically,
> > add virtio specific types
2014 Nov 24
2
[PATCH v3 04/41] virtio: memory access APIs
virtio 1.0 makes all memory structures LE, so
we need APIs to conditionally do a byteswap on BE
architectures.
To make it easier to check code statically,
add virtio specific types for multi-byte integers
in memory.
Add low level wrappers that do a byteswap conditionally, these will be
useful e.g. for vhost. Add high level wrappers that
query device endian-ness and act accordingly.
2014 Nov 24
2
[PATCH v3 04/41] virtio: memory access APIs
virtio 1.0 makes all memory structures LE, so
we need APIs to conditionally do a byteswap on BE
architectures.
To make it easier to check code statically,
add virtio specific types for multi-byte integers
in memory.
Add low level wrappers that do a byteswap conditionally, these will be
useful e.g. for vhost. Add high level wrappers that
query device endian-ness and act accordingly.
2014 Jan 16
6
[PATCH net-next v3 1/5] net: allow > 0 order atomic page alloc in skb_page_frag_refill
skb_page_frag_refill currently permits only order-0 page allocs
unless GFP_WAIT is used. Change skb_page_frag_refill to attempt
higher-order page allocations whether or not GFP_WAIT is used. If
memory cannot be allocated, the allocator will fall back to
successively smaller page allocs (down to order-0 page allocs).
This change brings skb_page_frag_refill in line with the existing
page allocation
2014 Jan 16
6
[PATCH net-next v3 1/5] net: allow > 0 order atomic page alloc in skb_page_frag_refill
skb_page_frag_refill currently permits only order-0 page allocs
unless GFP_WAIT is used. Change skb_page_frag_refill to attempt
higher-order page allocations whether or not GFP_WAIT is used. If
memory cannot be allocated, the allocator will fall back to
successively smaller page allocs (down to order-0 page allocs).
This change brings skb_page_frag_refill in line with the existing
page allocation
2014 Jan 16
13
[PATCH net-next v4 1/6] net: allow > 0 order atomic page alloc in skb_page_frag_refill
skb_page_frag_refill currently permits only order-0 page allocs
unless GFP_WAIT is used. Change skb_page_frag_refill to attempt
higher-order page allocations whether or not GFP_WAIT is used. If
memory cannot be allocated, the allocator will fall back to
successively smaller page allocs (down to order-0 page allocs).
This change brings skb_page_frag_refill in line with the existing
page allocation
2014 Jan 16
13
[PATCH net-next v4 1/6] net: allow > 0 order atomic page alloc in skb_page_frag_refill
skb_page_frag_refill currently permits only order-0 page allocs
unless GFP_WAIT is used. Change skb_page_frag_refill to attempt
higher-order page allocations whether or not GFP_WAIT is used. If
memory cannot be allocated, the allocator will fall back to
successively smaller page allocs (down to order-0 page allocs).
This change brings skb_page_frag_refill in line with the existing
page allocation
2014 Jan 17
7
[PATCH net-next v5 0/6] virtio-net: mergeable rx buffer size auto-tuning
The virtio-net device currently uses aligned MTU-sized mergeable receive
packet buffers. Network throughput for workloads with large average
packet size can be improved by posting larger receive packet buffers.
However, due to SKB truesize effects, posting large (e.g, PAGE_SIZE)
buffers reduces the throughput of workloads that do not benefit from GRO
and have no large inbound packets.
This
2014 Jan 17
7
[PATCH net-next v5 0/6] virtio-net: mergeable rx buffer size auto-tuning
The virtio-net device currently uses aligned MTU-sized mergeable receive
packet buffers. Network throughput for workloads with large average
packet size can be improved by posting larger receive packet buffers.
However, due to SKB truesize effects, posting large (e.g, PAGE_SIZE)
buffers reduces the throughput of workloads that do not benefit from GRO
and have no large inbound packets.
This
2014 Jan 17
7
[PATCH net-next v6 0/6] virtio-net: mergeable rx buffer size auto-tuning
The virtio-net device currently uses aligned MTU-sized mergeable receive
packet buffers. Network throughput for workloads with large average
packet size can be improved by posting larger receive packet buffers.
However, due to SKB truesize effects, posting large (e.g, PAGE_SIZE)
buffers reduces the throughput of workloads that do not benefit from GRO
and have no large inbound packets.
This
2014 Jan 17
7
[PATCH net-next v6 0/6] virtio-net: mergeable rx buffer size auto-tuning
The virtio-net device currently uses aligned MTU-sized mergeable receive
packet buffers. Network throughput for workloads with large average
packet size can be improved by posting larger receive packet buffers.
However, due to SKB truesize effects, posting large (e.g, PAGE_SIZE)
buffers reduces the throughput of workloads that do not benefit from GRO
and have no large inbound packets.
This
2005 Jul 28
10
dma_alloc_coherent issue with tg3 in x86_64 build
During boot of dom0, I get the following. Box is remote, so I''m
now waiting for proxy power button pusher ;-) tg3 init fails doing
dma_alloc_coherent (I assume this is from tg3_init_one -> tg3_test_dma ->
pci_alloc_consistent -> dma_alloc_coherent). Looks like an issue with
the amount of memory in dom0. Is this known?
thanks,
-chris
root (hd0,0)
Filesystem type is ext2fs,
2014 Nov 24
0
[PATCH v3 04/41] virtio: memory access APIs
On Mon, Nov 24, 2014 at 1:15 PM, Michael S. Tsirkin <mst at redhat.com> wrote:
> On Mon, Nov 24, 2014 at 01:03:24PM +0100, Geert Uytterhoeven wrote:
>> On Mon, Nov 24, 2014 at 12:52 PM, Michael S. Tsirkin <mst at redhat.com> wrote:
>> > virtio 1.0 makes all memory structures LE, so
>> > we need APIs to conditionally do a byteswap on BE
>> >
2013 Jan 28
16
PVH questions
Hello,
I''ve had a look at PVH support, and I have a few questions:
- events are still dispatched the PV way through the callback, right?
- I guess FPU errors don''t trigger an INT13, so I don''t need to handle
that?
- How about the console and store MFNs from the boot info? Are they
still MFNs, or actually PFNs?
- How about PV network in non-copy mode? It used to be
2008 Sep 08
3
Problem with install Boardcom driver
Hi,
I have to install Broadcom driver because the Dell Optiplex 330
running Centos 5.2 is not able to connect to the network.
I am trying to install a Broadcom driver, but I get the followng error:
[root at localhost tg3-3.85l]#
[root at localhost tg3-3.85l]# make
make -C /lib/modules/2.6.18-92.el5/build
SUBDIRS=/usr/src/Server/Linux/Driver/tg3-3.85l modules
make[1]: Entering directory
2014 Jan 16
0
[PATCH net-next v3 4/5] net-sysfs: add support for device-specific rx queue sysfs attributes
Extend existing support for netdevice receive queue sysfs attributes to
permit a device-specific attribute group. Initial use case for this
support will be to allow the virtio-net device to export per-receive
queue mergeable receive buffer size.
Signed-off-by: Michael Dalton <mwdalton at google.com>
---
include/linux/netdevice.h | 40 ++++++++++++++++++++++++++++++++++++----
net/core/dev.c
2014 Jan 16
0
[PATCH net-next v4 4/6] net-sysfs: add support for device-specific rx queue sysfs attributes
Extend existing support for netdevice receive queue sysfs attributes to
permit a device-specific attribute group. Initial use case for this
support will be to allow the virtio-net device to export per-receive
queue mergeable receive buffer size.
Signed-off-by: Michael Dalton <mwdalton at google.com>
---
v3->v4: Simplify by removing loop in get_netdev_rx_queue_index.
2007 Apr 18
2
[Bridge] tg3 bridge problems
Hello,
I've got a very strange problem. Lately I've been setting up my linux
servers for network (layer2) redundancy with a bridge interface containing
two ethernet interfaces connecting to two switches. So far I didn't have
any problems with it, but now a very strange thing happens with a new
server I'm installing. The server is an ibm x346 having two onboard
BCM5721 cards, the