similar to: [Bug 567] ulogd writes invalid len field in per-packet headers

On 16-06-29 08:52 PM, Jason Wang wrote: > This patch introduces a new event - NETDEV_CHANGE_TX_QUEUE_LEN, this > will be triggered when tx_queue_len. It could be used by net device > who want to do some processing at that time. An example is tun who may > want to resize tx array when tx_queue_len is changed. > > Signed-off-by: Jason Wang <jasowang at redhat.com> > ---

On 16-06-29 08:52 PM, Jason Wang wrote: > This patch introduces a new event - NETDEV_CHANGE_TX_QUEUE_LEN, this > will be triggered when tx_queue_len. It could be used by net device > who want to do some processing at that time. An example is tun who may > want to resize tx array when tx_queue_len is changed. > > Signed-off-by: Jason Wang <jasowang at redhat.com> > ---

This allows more requests to fit in the descriptor ring. Copying 1.7M kernel image 100 times (with sync between) Before: totsegs = 55661 totlen = 148859962 avg. 2674 After: totsegs = 36097 totlen = 139439355 avg: 3862 Unfortunately, this coalescing is done at blk_rq_map_sg() which is too late to be optimal: requests have already been limited to the value set by blk_queue_max_hw_segments().

This allows more requests to fit in the descriptor ring. Copying 1.7M kernel image 100 times (with sync between) Before: totsegs = 55661 totlen = 148859962 avg. 2674 After: totsegs = 36097 totlen = 139439355 avg: 3862 Unfortunately, this coalescing is done at blk_rq_map_sg() which is too late to be optimal: requests have already been limited to the value set by blk_queue_max_hw_segments().

On 2016?06?30? 13:12, Jason Wang wrote: > > > On 2016?06?30? 12:56, John Fastabend wrote: >> On 16-06-29 08:52 PM, Jason Wang wrote: >>> This patch introduces a new event - NETDEV_CHANGE_TX_QUEUE_LEN, this >>> will be triggered when tx_queue_len. It could be used by net device >>> who want to do some processing at that time. An example is tun who may

On 2016?06?30? 13:12, Jason Wang wrote: > > > On 2016?06?30? 12:56, John Fastabend wrote: >> On 16-06-29 08:52 PM, Jason Wang wrote: >>> This patch introduces a new event - NETDEV_CHANGE_TX_QUEUE_LEN, this >>> will be triggered when tx_queue_len. It could be used by net device >>> who want to do some processing at that time. An example is tun who may

Hi all: This series tries to switch to use skb array in tun. This is used to eliminate the spinlock contention between producer and consumer. The conversion was straightforward: just introdce a tx skb array and use it instead of sk_receive_queue. A minor issue is to keep the tx_queue_len behaviour, since tun used to use it for the length of sk_receive_queue. This is done through: - add the

Hi all: This series tries to switch to use skb array in tun. This is used to eliminate the spinlock contention between producer and consumer. The conversion was straightforward: just introdce a tx skb array and use it instead of sk_receive_queue. A minor issue is to keep the tx_queue_len behaviour, since tun used to use it for the length of sk_receive_queue. This is done through: - add the

On Wed, Aug 02, 2023 at 08:50:21PM -0500, Eric Blake wrote: > Previously, we had not been doing any validation of server extent > responses, which means a client query at an offset near the end of the > export can result in a buggy server sending a response longer than the > export length and potentially confusing the client. The NBD spec also > says that an extent length should be

Hi all: This series tries to switch to use skb array in tun. This is used to eliminate the spinlock contention between producer and consumer. The conversion was straightforward: just introdce a tx skb array and use it instead of sk_receive_queue. A minor issue is to keep the tx_queue_len behaviour, since tun used to use it for the length of sk_receive_queue. This is done through: - add the

Hi all: This series tries to switch to use skb array in tun. This is used to eliminate the spinlock contention between producer and consumer. The conversion was straightforward: just introdce a tx skb array and use it instead of sk_receive_queue. A minor issue is to keep the tx_queue_len behaviour, since tun used to use it for the length of sk_receive_queue. This is done through: - add the

Hello all, Here is a new iteration of the patch series that implements a transport for guest and host communications. The code has been updated to reuse the virtio-console device instead of creating a new virtio-serial device. I've tested for compatibility (old qemu & new kernel, new qemu & old kernel, new qemu & new kernel) and it all works fine. There are a few items on my

Hello all, Here is a new iteration of the patch series that implements a transport for guest and host communications. The code has been updated to reuse the virtio-console device instead of creating a new virtio-serial device. I've tested for compatibility (old qemu & new kernel, new qemu & old kernel, new qemu & new kernel) and it all works fine. There are a few items on my

Hi Max/DTrace list, > At any rate, without the -C, I can''t use #include <sys/stream.h>. > Without the #include <sys/stream.h>, I can''t use the M_DATA. > As it is, I get the following: > > # ./strrput.d 0xd595a6c0 <-- this is a vnode for a socket > ftp is using (not important here) > dtrace: failed to compile script ./strrput.d: line 7: >

We free transmitted packets in ndo_start_xmit() in the past to get better performance in the past. One side effect is that skb_orphan() needs to be called in ndo_start_xmit() which makes sk_wmem_alloc not accurate in fact. For TCP protocol, this means several optimization could not work well such as TCP small queue and auto corking. This can lead extra low throughput of small packets stream.

We free transmitted packets in ndo_start_xmit() in the past to get better performance in the past. One side effect is that skb_orphan() needs to be called in ndo_start_xmit() which makes sk_wmem_alloc not accurate in fact. For TCP protocol, this means several optimization could not work well such as TCP small queue and auto corking. This can lead extra low throughput of small packets stream.

WARNING: This is not compatible with the previous lz4 patchset. If you''re using experimental compression that isn''t in mainline kernels, be prepared to backup and restore or decompress before upgrading, and have backups in case it eats data (which appears not to be a problem any more, but has been during development). These patches add lz4 and lz4hc compression

I am looking for ulog-2.0.x packages and the best I have been able to find [for CentOS6] has been ulog-2.0.0 (which is not an exciting prospect for .0 reasons). Is anyone aware of ulogd packages for CentOS6 [x86_64]? I am kind of surprised this isn't standard fair. -- Adam Tauno Williams <mailto:awilliam at whitemice.org> GPG D95ED383 Systems Administrator, Python Developer, LPI /

This patch introduces a new event - NETDEV_CHANGE_TX_QUEUE_LEN, this will be triggered when tx_queue_len. It could be used by net device who want to do some processing at that time. An example is tun who may want to resize tx array when tx_queue_len is changed. Cc: John Fastabend <john.r.fastabend at intel.com> Signed-off-by: Jason Wang <jasowang at redhat.com> ---

Hi use traffic shaping on my local lan and it keeps all drops packets by logging them to mysql via ulogd. Since there is windows and apple users on the network I would like to have their "computer names" instead of ip address to make for easy accounting. Does anyone know of a script or tool to get the ip address of a drop packet and turn it into a computer name (via wins or something