search for: ifce

>>>>> Saikat DebRoy writes: > On Thursday, Sep 25, 2003, at 05:26 US/Eastern, CanisMaior@web.de wrote: >> Bugs compiling R-1.7.1 with Intel compilers icc and ifc, >> on x86-computer (Pentium IV) and linux operating system >> > Many of those bugs can be fixed by using appropriate configure options. > Some of the warnings are serious, but they quite a

define xen paravirtualized instructions for hand written assembly code. Signed-off-by: Yaozu (Eddie) Dong <eddie.dong at intel.com> Signed-off-by: Isaku Yamahata <yamahata at valinux.co.jp> Cc: Akio Takebe <takebe_akio at jp.fujitsu.com> --- include/asm-ia64/xen/inst.h | 447 +++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 447 insertions(+), 0 deletions(-) create

Bugs compiling R-1.7.1 with Intel compilers icc and ifc, on x86-computer (Pentium IV) and linux operating system Hello, as there aren't many reports about that issue, I'll give a little report here. (Hope I don't bother anyone) The best thing about using icc and ifc are the warnings, because it is said that the Intel compilers are stricter and give more precise warnings than gcc.

On 2019/10/16 ??9:36, Zhu Lingshan wrote: > failed to send to kvm list, resend, sorry for the inconvenience. > > THanks, > BR > Zhu Lingshan > > On 10/16/2019 9:30 AM, Zhu Lingshan wrote: >> Hi all: >> ? This series intends to introduce Intel IFC VF NIC driver for Vhost >> Data Plane Acceleration. >> ? Here comes two main parts, one is ifcvf_base layer,

>>>>> CanisMaior writes: > Bugs compiling R-1.7.1 with Intel compilers icc and ifc, > on x86-computer (Pentium IV) and linux operating system > Hello, > as there aren't many reports about that issue, I'll give a little > report here. (Hope I don't bother anyone) > The best thing about using icc and ifc are the warnings, because > it is said that

On Thu, Mar 26, 2020 at 3:08 PM Jason Wang <jasowang at redhat.com> wrote: > > From: Zhu Lingshan <lingshan.zhu at intel.com> > > This commit introduced two layers to drive IFC VF: > > (1) ifcvf_base layer, which handles IFC VF NIC hardware operations and > configurations. > > (2) ifcvf_main layer, which complies to VDPA bus framework, >

Hi all i have big problem,I am newbie and my english is bad,but i know you can help solve my problem. I have box with gentoo,I live in latvia and i have 2 ISP: One isp gives me ip range from 62.85.71.1-62.85.71.15 (62.85.71.1 is gateway) but there is only latvian trafik - no other countries (link is 2 mbit Asinhronus dsl) and other isp who gives me one ip from dhcp adn there ios no trafik

On 2019/10/22 ??2:53, Zhu Lingshan wrote: > > On 10/21/2019 6:19 PM, Jason Wang wrote: >> >> On 2019/10/21 ??5:53, Zhu, Lingshan wrote: >>> >>> On 10/16/2019 6:19 PM, Jason Wang wrote: >>>> >>>> On 2019/10/16 ??9:30, Zhu Lingshan wrote: >>>>> This commit introduced IFC VF operations for vdpa, which complys to

On 2019/10/23 ??2:19, Zhu, Lingshan wrote: > > On 10/22/2019 9:05 PM, Jason Wang wrote: >> >> On 2019/10/22 ??2:53, Zhu Lingshan wrote: >>> >>> On 10/21/2019 6:19 PM, Jason Wang wrote: >>>> >>>> On 2019/10/21 ??5:53, Zhu, Lingshan wrote: >>>>> >>>>> On 10/16/2019 6:19 PM, Jason Wang wrote:

Hi, I have downloaded rstp from sourceforge and I get a segfaults when running the daemon. This is the line where the problem arises: TST(ifc->master->stp_up,); just at the beginning of function: void bridge_bpdu_rcv(int if_index, const unsigned char *data, int len) in file bridge_track.c -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi!! I found your ipconfig stuff in the udev rpm in SuSE 9.1. I'm about to setup a initramfs (pretty cool - much better than initrd) to boot linux diskless clients over the net. All the tools I would need, seem to be there with ipconfig/nfsmount ... I like to use the information I get from PXE/syslinux or Etherboot writing something like:

If user did not configure any vdpa drivers, neither vhost nor virtio vdpa are going to be useful. So there's no point in prompting for these and selecting vdpa core automatically. Simplify configuration by making virtio and vhost vdpa drivers depend on vdpa menu entry. Once done, we no longer need a separate menu entry, so also get rid of this. While at it, fix up the IFC entry: VDPA->vDPA

On 2019/10/22 ??12:31, Simon Horman wrote: > On Mon, Oct 21, 2019 at 05:55:33PM +0800, Zhu, Lingshan wrote: >> On 10/16/2019 5:53 PM, Simon Horman wrote: >>> Hi Zhu, >>> >>> thanks for your patch. >>> >>> On Wed, Oct 16, 2019 at 09:10:40AM +0800, Zhu Lingshan wrote: > ... > >>>> +static void ifcvf_read_dev_config(struct

Hi [and apologies for misusing the list for some statistical software related conference ads], The IFCS 2009 (International Federation of Classification Societies) Conference takes place in Dresden Germany: March 13-18, 2009. The conference and in particular its section on `Data Analysis Software' may be of interest to those R useRs and developeRs who are working in the area of

Dear R-devel, I'm trying to compile R-1.9.0beta (2004-03-31) with the PGI compilers (15-day free evaluation: after the 15 days the binaries will stop working). I'm running into some problems, that I hope some can offer pointers. 1. After configure, the FLIBS include /usr/local/lib' --- note the extra '. I had to manually delete it in a couple of places. In a previous thread on

On Wed, 16 Oct 2019 09:03:17 +0800 Zhu Lingshan <lingshan.zhu at intel.com> wrote: > +int ifcvf_init_hw(struct ifcvf_hw *hw, struct pci_dev *dev) > +{ > + int ret; > + u8 pos; > + struct virtio_pci_cap cap; > + u32 i; > + u16 notify_off; For network code, the preferred declaration style is reverse christmas tree.

On Wed, 16 Oct 2019 09:03:17 +0800 Zhu Lingshan <lingshan.zhu at intel.com> wrote: > + IFC_INFO(&dev->dev, "PCI capability mapping:\n" > + "common cfg: %p\n" > + "notify base: %p\n" > + "isr cfg: %p\n" > + "device cfg: %p\n" > + "multiplier: %u\n", > + hw->common_cfg, > +

On 2019/10/16 ??9:30, Zhu Lingshan wrote: > + */ > +#define IFCVF_TRANSPORT_F_START 28 > +#define IFCVF_TRANSPORT_F_END 34 > + > +#define IFC_SUPPORTED_FEATURES \ > + ((1ULL << VIRTIO_NET_F_MAC) | \ > + (1ULL << VIRTIO_F_ANY_LAYOUT) | \ > + (1ULL << VIRTIO_F_VERSION_1) | \ > + (1ULL << VHOST_F_LOG_ALL) | \ Let's avoid using

On 2019/10/21 ??5:57, Zhu, Lingshan wrote: > > On 10/16/2019 4:45 PM, Jason Wang wrote: >> >> On 2019/10/16 ??9:30, Zhu Lingshan wrote: >>> + */ >>> +#define IFCVF_TRANSPORT_F_START 28 >>> +#define IFCVF_TRANSPORT_F_END?? 34 >>> + >>> +#define IFC_SUPPORTED_FEATURES \ >>> +??????? ((1ULL << VIRTIO_NET_F_MAC)??????????? |

On 2019/10/23 ??5:24, Zhu, Lingshan wrote: >>>>> >>>>> >>>>> set_config/get_config is missing. It looks to me they are not >>>>> hard, just implementing the access to dev_cfg. It's key to make >>>>> kernel virtio driver to work. >>>>> >>>>> And in the new version of virito-mdev, features