search for: stag

...fixed] tx-lockless: off [fixed] netns-local: off [fixed] tx-gso-robust: off [fixed] tx-fcoe-segmentation: off [fixed] tx-gre-segmentation: off [fixed] tx-udp_tnl-segmentation: off [fixed] fcoe-mtu: off [fixed] tx-nocache-copy: on loopback: off [fixed] rx-fcs: off [fixed] rx-all: off [fixed] tx-vlan-stag-hw-insert: off [fixed] rx-vlan-stag-hw-parse: off [fixed] rx-vlan-stag-filter: off [fixed]

In my Linux VM, I am unable to change scatter-gather / tx-checksumming / TCP-segmentation offload features by ethtool command. I am using virtio nic with vhostuser port backend. It shows me an error: Cannot change tx-checksumming Cannot change scatter-gather Cannot change tcp-segmentation offload Could not change any device features Ony running command ethtool -k ens3, I get the following:

Hi Arnaud, hi developers, attach there is the patch for riello drivers. Can you tell me if there is other to change in order to accomplish your rules and if the steps I have followed to create the patch are all rights? Cheers, Elio Parisi. Elio Parisi Centro Ricerche RPS SpA Viale Europa, 7 37045 Legnago VR Tel. +39 0442 635811 Fax. +39 0442 635934 Skype Id: - Voip: E-mail: E.Parisi

Hi. Thank you for comments on asm code paravirtualization. Its direction is getting clear. Although it hasn't been finished yet, I'd like to start discussion on ia64 intrinsics paravirtualization. This patch set is just for discussion so that it is a subset of xen Linux/ia64 domU paravirtualization, not self complete. You can get the full patched tree by typing git clone

Hi. Thank you for comments on asm code paravirtualization. Its direction is getting clear. Although it hasn't been finished yet, I'd like to start discussion on ia64 intrinsics paravirtualization. This patch set is just for discussion so that it is a subset of xen Linux/ia64 domU paravirtualization, not self complete. You can get the full patched tree by typing git clone

This patch set is intended for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for binary patch optimization for paravirt_ops. The binary patch optimization is important on native case because the paravirt_ops overhead can be reduced by converting indirect

This patch set is intended for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for binary patch optimization for paravirt_ops. The binary patch optimization is important on native case because the paravirt_ops overhead can be reduced by converting indirect

This patch set is intended for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for binary patch optimization for paravirt_ops which depends on the patch series I sent out, ia64/pv_ops, xen: more paravirtualization. The binary patch optimization is important on

This patch set is intended for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for binary patch optimization for paravirt_ops which depends on the patch series I sent out, ia64/pv_ops, xen: more paravirtualization. The binary patch optimization is important on

This patch set is for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for binary patch optimization for paravirt_ops which depends on the patch series I sent out, ia64/pv_ops, xen: more paravirtualization. The binary patch optimization is important on native

This patch set is for the next merge window. They are just enhancements of the already merged patches or ia64 porting from x86 paravirt techniques and that their quality is enough for merge. This patch set is for binary patch optimization for paravirt_ops which depends on the patch series I sent out, ia64/pv_ops, xen: more paravirtualization. The binary patch optimization is important on native

This patch set is for binary patch optimization for paravirt_ops. The binary patch optimization is important on native case because the paravirt_ops overhead can be reduced by converting indirect call into in-place execution or direct call. The first patch imports helper functions which themselves doesn't interesting things. The second patch replaces the indirect function calls with a

This patch set is for binary patch optimization for paravirt_ops. The binary patch optimization is important on native case because the paravirt_ops overhead can be reduced by converting indirect call into in-place execution or direct call. The first patch imports helper functions which themselves doesn't interesting things. The second patch replaces the indirect function calls with a

...helps. I did a little poking around the code but thought I would ask here before investigating more. Is this a know problem? Cheers, Tom Objects left on heap after mechanizing a single page and doing a garbage collection: Hpricot::Text 18 | delta 18 Hpricot::STag 12 | delta 12 Hpricot::Elem 12 | delta 12 Hpricot::ETag 8 | delta 8 WWW::Mechanize::List 5 | delta 5 WWW::Mechanize::Link 2 | delta 2 Mat...

...on deserved holidays), around Thursday or Friday. Apart from what is already there, I'd like to see: - the latest nut-scanner developments (lowered runtime deps, thanks to libltdl, and IPMI scan) - the krauler lang_id patch - a few warning fixes (from Regid), if possible If you have anything stagging on your side, or if I've missed something, please reply back so that I can take it into account. There will quite probably cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian...

Hi! I found that if upsd had been running, then another "upsd" was typed. The upsd.pid file would be deleted and the previous upsd could not quit normally unless using "pkill upsd". The second upsd detects port conflict, and then deletes the upsd.pid. As a result, any further "upsd -c stop" or "upsd -c reload" would detect no upsd.pid and simply quit. I

Fellows, I've had this stagging for too long: For some writable (RW) variables, that support ranges of values, ENUM and STRING are too limited and not adapted. So it's worth adding a new RANGE type, with the needed driver function (dstate_addrange()) and server / client support. Thus, I'm intending to do the followin...

Hi, I'd like to inform You that this UPS communicates well via the serial port. I haven't tested USB, and no shutdown testing so far, however, I hope it will run well. HP R5000 upsc output: ambient.temperature: 27.4 ambient.temperature.high: 45 battery.charge: 99.0 battery.runtime: 536 battery.voltage: 236.3 device.mfr: Eaton device.model: HP R5000 5000i device.serial: 3C81520083

...eplied to Greg in the past couple of days, some patches have been applied to apcsmart... I would be grateful if you could both counter check if everything is fine. I'm still flushing my queues for 2.6.4, and still naively hope to release it by the end of next week. If you, or other, have some stagging patches that must go into 2.6.4, it's the right time to send it. @Greg: here is the list of postponed patch, with rationales. If you feel some of this should not wait for 2.8.0, tell me back. postponed - 8-10 (pyperl / snmp...) => need tree / deps handling revamp + [PATCH] "oo...

...more generic nut names (ie move from ups.* to device.* in nut-names.txt) - move existing ups.{model,mfr,...} to device.* in drivers - move ups.status to device.status - with compat mapping counterparts (device.* also to ups.* if (device.type == ups)) * standard flow of bug-fixes and stagging improvements... priority 2 (best effort) * powerchain step 2: support in upsmon * Windows port integration: if possible, need step refactoring / enhancement / more testing * better Mac OS X integration (including StartupItem initscript, .pmdoc packaging script and ?) I realize that thi...