Displaying 20 results from an estimated 700 matches similar to: "CentOS-announce Digest, Vol 147, Issue 1"
2017 May 04
0
CEEA-2017:1194 CentOS 7 kmod-redhat-ixgbevf Enhancement Update
CentOS Errata and Enhancement Advisory 2017:1194
Upstream details at : https://rhn.redhat.com/errata/RHEA-2017-1194.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
ead8dfcb3828518aed74380b77d990bb193ee63417354c20c4b91b2ef95a720f kmod-redhat-ixgbevf-3.2.2_k_rh7.4_z-1.el7_3.x86_64.rpm
Source:
2017 May 04
0
CEEA-2017:1194 CentOS 7 kmod-redhat-ixgbe Enhancement Update
CentOS Errata and Enhancement Advisory 2017:1194
Upstream details at : https://rhn.redhat.com/errata/RHEA-2017-1194.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
cd47bdab22ce9c387beaf066c0e36d63633b07bfcbcad4bda1dac53c74a095e2 kmod-redhat-ixgbe-4.4.0_k_rh7.4_z-2.el7_3.x86_64.rpm
Source:
2012 Sep 10
9
issue using SRIOV "Unable to start - perhaps the PF driver is not up yet", while PF driver is actually up
Hi,
I am trying to use SRIOV, usnig xen 4.0 on debian.
On my dom0, xm pci-list-assignable-devices show that
0000:0f:10.0
0000:0f:10.2
0000:0f:10.4
0000:0f:10.6
0000:0f:11.2
0000:0f:11.4
0000:0f:11.6
these virtual interfaces correspond to eth2,
i attach 0f:10.0 to a domU ubuntu machine, xm pci-attach ubuntu 0f:10.0
on my dom0 machine, i can ping other machine using eth2, (implying PF on
eth2
2012 Sep 10
9
issue using SRIOV "Unable to start - perhaps the PF driver is not up yet", while PF driver is actually up
Hi,
I am trying to use SRIOV, usnig xen 4.0 on debian.
On my dom0, xm pci-list-assignable-devices show that
0000:0f:10.0
0000:0f:10.2
0000:0f:10.4
0000:0f:10.6
0000:0f:11.2
0000:0f:11.4
0000:0f:11.6
these virtual interfaces correspond to eth2,
i attach 0f:10.0 to a domU ubuntu machine, xm pci-attach ubuntu 0f:10.0
on my dom0 machine, i can ping other machine using eth2, (implying PF on
eth2
2013 Aug 14
5
pci passthrough don't work with kernels > 3.8
Hi,
trying to pass through a intel x520 VF on a Dell R620, I''m getting in domU:
[ 58.162639] pci 0000:00:00.6: address space collision: [mem 0xd500c000-0xd500ffff 64bit pref] conflicts with System RAM [mem 0x00100000-0x176ffffff]
[ 58.162654] pcifront pci-0: Could not claim resource 0000:00:00.6/0! Device offline. Try using e820_host=1 in the guest config.
and in dom0
(XEN)
2017 Nov 30
0
[RFC] virtio-net: help live migrate SR-IOV devices
On 2017?11?29? 03:27, Jesse Brandeburg wrote:
> Hi, I'd like to get some feedback on a proposal to enhance virtio-net
> to ease configuration of a VM and that would enable live migration of
> passthrough network SR-IOV devices.
>
> Today we have SR-IOV network devices (VFs) that can be passed into a VM
> in order to enable high performance networking direct within the VM.
2017 Nov 30
0
[RFC] virtio-net: help live migrate SR-IOV devices
On Wed, 29 Nov 2017 19:51:38 -0800
Jakub Kicinski <jakub.kicinski at netronome.com> wrote:
> On Thu, 30 Nov 2017 11:29:56 +0800, Jason Wang wrote:
> > On 2017?11?29? 03:27, Jesse Brandeburg wrote:
> > > Hi, I'd like to get some feedback on a proposal to enhance
> > > virtio-net to ease configuration of a VM and that would enable
> > > live migration
2017 Nov 30
0
[RFC] virtio-net: help live migrate SR-IOV devices
On Wed, Nov 29, 2017 at 07:51:38PM -0800, Jakub Kicinski wrote:
> On Thu, 30 Nov 2017 11:29:56 +0800, Jason Wang wrote:
> > On 2017?11?29? 03:27, Jesse Brandeburg wrote:
> > > Hi, I'd like to get some feedback on a proposal to enhance virtio-net
> > > to ease configuration of a VM and that would enable live migration of
> > > passthrough network SR-IOV
2017 Nov 28
5
[RFC] virtio-net: help live migrate SR-IOV devices
Hi, I'd like to get some feedback on a proposal to enhance virtio-net
to ease configuration of a VM and that would enable live migration of
passthrough network SR-IOV devices.
Today we have SR-IOV network devices (VFs) that can be passed into a VM
in order to enable high performance networking direct within the VM.
The problem I am trying to address is that this configuration is
generally
2017 Nov 28
5
[RFC] virtio-net: help live migrate SR-IOV devices
Hi, I'd like to get some feedback on a proposal to enhance virtio-net
to ease configuration of a VM and that would enable live migration of
passthrough network SR-IOV devices.
Today we have SR-IOV network devices (VFs) that can be passed into a VM
in order to enable high performance networking direct within the VM.
The problem I am trying to address is that this configuration is
generally
2017 Nov 30
1
[RFC] virtio-net: help live migrate SR-IOV devices
On Thu, 30 Nov 2017 15:54:40 +0200, Michael S. Tsirkin wrote:
> On Wed, Nov 29, 2017 at 07:51:38PM -0800, Jakub Kicinski wrote:
> > On Thu, 30 Nov 2017 11:29:56 +0800, Jason Wang wrote:
> > > On 2017?11?29? 03:27, Jesse Brandeburg wrote:
> > > > Hi, I'd like to get some feedback on a proposal to enhance virtio-net
> > > > to ease configuration of a
2017 Nov 30
1
[RFC] virtio-net: help live migrate SR-IOV devices
On Thu, 30 Nov 2017 15:54:40 +0200, Michael S. Tsirkin wrote:
> On Wed, Nov 29, 2017 at 07:51:38PM -0800, Jakub Kicinski wrote:
> > On Thu, 30 Nov 2017 11:29:56 +0800, Jason Wang wrote:
> > > On 2017?11?29? 03:27, Jesse Brandeburg wrote:
> > > > Hi, I'd like to get some feedback on a proposal to enhance virtio-net
> > > > to ease configuration of a
2017 Nov 30
4
[RFC] virtio-net: help live migrate SR-IOV devices
On Thu, 30 Nov 2017 11:29:56 +0800, Jason Wang wrote:
> On 2017?11?29? 03:27, Jesse Brandeburg wrote:
> > Hi, I'd like to get some feedback on a proposal to enhance virtio-net
> > to ease configuration of a VM and that would enable live migration of
> > passthrough network SR-IOV devices.
> >
> > Today we have SR-IOV network devices (VFs) that can be passed
2017 Nov 30
4
[RFC] virtio-net: help live migrate SR-IOV devices
On Thu, 30 Nov 2017 11:29:56 +0800, Jason Wang wrote:
> On 2017?11?29? 03:27, Jesse Brandeburg wrote:
> > Hi, I'd like to get some feedback on a proposal to enhance virtio-net
> > to ease configuration of a VM and that would enable live migration of
> > passthrough network SR-IOV devices.
> >
> > Today we have SR-IOV network devices (VFs) that can be passed
2017 Nov 30
2
[RFC] virtio-net: help live migrate SR-IOV devices
On 30 November 2017 at 05:29, Jason Wang <jasowang at redhat.com> wrote:
>
>
> On 2017?11?29? 03:27, Jesse Brandeburg wrote:
>>
>> Hi, I'd like to get some feedback on a proposal to enhance virtio-net
>> to ease configuration of a VM and that would enable live migration of
>> passthrough network SR-IOV devices.
>>
>> Today we have SR-IOV
2017 Nov 30
2
[RFC] virtio-net: help live migrate SR-IOV devices
On 30 November 2017 at 05:29, Jason Wang <jasowang at redhat.com> wrote:
>
>
> On 2017?11?29? 03:27, Jesse Brandeburg wrote:
>>
>> Hi, I'd like to get some feedback on a proposal to enhance virtio-net
>> to ease configuration of a VM and that would enable live migration of
>> passthrough network SR-IOV devices.
>>
>> Today we have SR-IOV
2014 May 08
0
[PATCH] net: get rid of SET_ETHTOOL_OPS
I think that it may be appropriate to submit this patch for linux-next
instead of 3.15-rc4...
On Thu, May 8, 2014 at 1:53 PM, Wilfried Klaebe
<w-lkml at lebenslange-mailadresse.de> wrote:
> Dave Miller mentioned he'd like to see SET_ETHTOOL_OPS gone.
> This does that.
>
> Compile tested only, but I'd seriously wonder if this broke anything.
>
> Suggested-by: Dave
2020 Sep 09
17
[trivial PATCH] treewide: Convert switch/case fallthrough; to break;
fallthrough to a separate case/default label break; isn't very readable.
Convert pseudo-keyword fallthrough; statements to a simple break; when
the next label is case or default and the only statement in the next
label block is break;
Found using:
$ grep-2.5.4 -rP --include=*.[ch] -n "fallthrough;(\s*(case\s+\w+|default)\s*:\s*){1,7}break;" *
Miscellanea:
o Move or coalesce a
2014 May 11
0
[PATCH] [resend] net: get rid of SET_ETHTOOL_OPS
SET_ETHTOOL_OPS is equivalent to :
#define SET_ETHTOOL_OPS(netdev,ops) \
( (netdev)->ethtool_ops = (ops) )
how it makes difference removing this code and replacing with the
code mentioned ?
On Sun, May 11, 2014 at 5:42 AM, Wilfried Klaebe
<w-lkml at lebenslange-mailadresse.de> wrote:
> net: get rid of SET_ETHTOOL_OPS
>
> Dave Miller mentioned he'd like to see
2014 May 11
0
[PATCH] [resend] net: get rid of SET_ETHTOOL_OPS
SET_ETHTOOL_OPS is equivalent to :
#define SET_ETHTOOL_OPS(netdev,ops) \
( (netdev)->ethtool_ops = (ops) )
how it makes difference removing this code and replacing with the
code mentioned ?
On Sun, May 11, 2014 at 5:42 AM, Wilfried Klaebe
<w-lkml at lebenslange-mailadresse.de> wrote:
> net: get rid of SET_ETHTOOL_OPS
>
> Dave Miller mentioned he'd like to see