search for: eqe

...; + return 0; > >> +} > >> + > >> +static int event_handler(struct notifier_block *nb, unsigned long event, void *param) > >> +{ > >> + struct mlx5_vdpa_net *ndev = container_of(nb, struct mlx5_vdpa_net, nb); > >> + struct mlx5_eqe *eqe = param; > >> + int ret = NOTIFY_DONE; > >> + > >> + if (event == MLX5_EVENT_TYPE_PORT_CHANGE) { > >> + switch (eqe->sub_type) { > >> + case MLX5_PORT_CHANGE_SUBTYPE_DOWN: > >> + case...

...struct ast_cli_entry *) 0x81197a0 x = 2 dup = 0x8137cc0 "reload" tws = 0 #5 0x080aef0f in action_command (s=0x81ead18, m=0xbddfaac0) at manager.c:927 No locals. #6 0x080b3ee4 in process_message (s=0x81ead18, m=0xbddfaac0) at manager.c:1305 ret = 0 eqe = (struct eventqent *) 0x0 action = "Command", '\0' <repeats 72 times> tmp = (struct manager_action *) 0x8144818 idText = "ActionID: 2007-01-03 15:17:39.165755\r\n", '\0' <repeats 217 times> iabuf = "216.187.141.25...

I have a epox nforce2 motherboard and it has a phy nic built in but I can't use it. when will working driver be available??

I'm building another server and must decide on scsi card the tekram looks very promising to me but need to know if it will be supported or not in 4.8 or 5.1. server will be used of mysql / apache. any info or suggestions as to scsi cards would be great. thx in advance. Sign, Eriq

Hello all, I had setup shorewall before succesfully with a normal LAN to internet connection. Now I''m connected to the internet via VPN and I got problems with configuring Shorewall. Any help is appreciated. This is my setup: - Gentoo Linux laptop (kernel gentoo-dev-sources-2.6.8.1) with Shorewall 2.0.4 (setup for Standalone one interface) and iptables 1.2.11 - VPN client is

This patchset is pre-requisite to export and provision device config attributes and features for vdpa live migration, in a way backward and forward compatibility can be retained. The follow up work [1] will need to be built around the new feature provisioning uAPI, with which it's easier to formalize migration compatibility support at the driver level. Thanks, -Siwei [1] [PATCH v3 0/4] vDPA:

This patchset is pre-requisite to export and provision device config attributes and features for vdpa live migration, in a way backward and forward compatibility can be retained. The follow up work [1] will need to be built around the new feature provisioning uAPI, with which it's easier to formalize migration compatibility support at the driver level. Thanks, -Siwei [1] [PATCH v3 0/4] vDPA:

This patchset is pre-requisite to export and provision device config attributes and features for vdpa live migration, in a way backward and forward compatibility can be retained. The follow up work [1] will need to be built around the new feature provisioning uAPI, with which it's easier to formalize migration compatibility support at the driver level. Thanks, -Siwei [1] [PATCH v3 0/4] vDPA:

This patchset is pre-requisite to export and provision device config attributes and features for vdpa live migration, in a way backward and forward compatibility can be retained. The follow up work [1] will need to be built around the new feature provisioning uAPI, with which it's easier to formalize migration compatibility support at the driver level. Thanks, -Siwei [1] [PATCH v3 0/4] vDPA:

...ueue *mvq, int num) > +{ > + mlx5_cq_set_ci(&mvq->cq.mcq); > + rx_post(&mvq->vqqp, num); > + if (mvq->event_cb.callback) > + mvq->event_cb.callback(mvq->event_cb.private); > +} > + > +static void mlx5_vdpa_cq_comp(struct mlx5_core_cq *mcq, struct mlx5_eqe *eqe) > +{ > + struct mlx5_vdpa_virtqueue *mvq = container_of(mcq, struct mlx5_vdpa_virtqueue, cq.mcq); > + struct mlx5_vdpa_net *ndev = mvq->ndev; > + void __iomem *uar_page = ndev->mvdev.res.uar->map; > + int num = 0; > + > + while (!mlx5_vdpa_poll_one(&mvq->c...

Hello list. I'm trying to rebuild the 2.6.9.67.0.20.EL kernel, but it fails even without modifications. How did I try it? Created a (non-root) build environment (not a mock ) Installed the kernel.scr.rpm and did a rpmbuild -ba --target=`uname -m` kernel-2.6.spec 2> prep-err.log | tee prep-out.log The build failed at the end: Processing files: kernel-xenU-devel-2.6.9-67.0.20.EL Checking

when will they add the driver to this nic card? I have an nforce2 mb by epox that has this nic and I can't use it at all :(