search for: deivce

Hello all, I recently ran over following issue ( the description is out of necessity bit lengthy): I have corrupted partition with ext3 filesystem oni t, fortunately enough partition was mirrored, so that I was able to dd the the mirroed partiton to the file like this: dd bs=512 if=/dev/<where_the_mirrored_partition_is> of=some_file and write the content to the primary partition like this:

On Thu, Sep 05, 2019 at 03:48:56PM -0400, Vivek Goyal wrote: > This object is used both by fuse_connection as well virt device. So make > this object reference counted and that makes it easy to define life cycle > of the object. > > Now deivce can be removed while filesystem is still mounted. This will > cleanup all the virtqueues but virtio_fs object will still be around and > will be cleaned when filesystem is unmounted and sb/fc drops its reference. > > Removing a device also stops all virt queues and any new reuqest gets...

On Thu, Sep 05, 2019 at 03:48:56PM -0400, Vivek Goyal wrote: > This object is used both by fuse_connection as well virt device. So make > this object reference counted and that makes it easy to define life cycle > of the object. > > Now deivce can be removed while filesystem is still mounted. This will > cleanup all the virtqueues but virtio_fs object will still be around and > will be cleaned when filesystem is unmounted and sb/fc drops its reference. > > Removing a device also stops all virt queues and any new reuqest gets...

Some deivces do not free the old tx skbs immediately after it has been sent (usually in tx interrupt). One such example is virtio-net which optimizes for virt and only free the possible old tx skbs during the next packet sending. This would lead the pktgen to wait forever in the refcount of the skb if no other...

Some deivces do not free the old tx skbs immediately after it has been sent (usually in tx interrupt). One such example is virtio-net which optimizes for virt and only free the possible old tx skbs during the next packet sending. This would lead the pktgen to wait forever in the refcount of the skb if no other...

...my website http://vieka.com/. Because some of the Handheld OSs don't have the ability to access Windows share resource, specifically, the new Pocket PC by Microsoft, I would like to add this capability to the handheld device. There might be some other platform that needs a client for Handheld deivce, for example, Palm OS, or Linux base Handheld device. But I do not have plan to port smbclient to those platforms at this moment. As you all know, resource in handheld device is very limited. There might be a need to greatly modify and simplify the code. Obviously, Microsoft might come out with th...

...Hajnoczi wrote: > On Thu, Sep 05, 2019 at 03:48:56PM -0400, Vivek Goyal wrote: > > This object is used both by fuse_connection as well virt device. So make > > this object reference counted and that makes it easy to define life cycle > > of the object. > > > > Now deivce can be removed while filesystem is still mounted. This will > > cleanup all the virtqueues but virtio_fs object will still be around and > > will be cleaned when filesystem is unmounted and sb/fc drops its reference. > > > > Removing a device also stops all virt queues and...

...uf, index, priv->cqe_size) + factor; > ``` > > It seems that although they have a completion > queue, they are still using the ring in order. I guess so (at least from the above bits). Git grep -i "out of order" in drivers/net gives some hints. Looks like there're few deivces do this. > I guess maybe storage device may want OOO. Right, some iSCSI did. But tracking them elsewhere is not only for OOO. Spec said: for element address " In a used descriptor, Element Address is unused. " for Next flag: " For example, if descriptors are used in the s...

...uf, index, priv->cqe_size) + factor; > ``` > > It seems that although they have a completion > queue, they are still using the ring in order. I guess so (at least from the above bits). Git grep -i "out of order" in drivers/net gives some hints. Looks like there're few deivces do this. > I guess maybe storage device may want OOO. Right, some iSCSI did. But tracking them elsewhere is not only for OOO. Spec said: for element address " In a used descriptor, Element Address is unused. " for Next flag: " For example, if descriptors are used in the s...

These data structures should go away when virtio_fs object is going away. When deivce is going away, we need to just make sure virtqueues can go away and after that none of the code accesses vq and all the requests get error. So allocate memory for virtio_fs and virtio_fs_vq normally and free it at right time. This patch still frees up memory during device remove time. A later pat...

...0:03PM +0800, piaojun wrote: > > > On 2019/9/6 3:48, Vivek Goyal wrote: > > This object is used both by fuse_connection as well virt device. So make > > this object reference counted and that makes it easy to define life cycle > > of the object. > > > > Now deivce can be removed while filesystem is still mounted. This will > > cleanup all the virtqueues but virtio_fs object will still be around and > > will be cleaned when filesystem is unmounted and sb/fc drops its reference. > > > > Removing a device also stops all virt queues and...

...asterisk with an active ISDN B1 AVM Card (german vendor) and it works fine, various SIP clients (IP fon snom, xlite under MacOSX) and also incoming and outgoing connectins. Ok. No problem. After that I configured a CP7940G with a MGCP IOS. It's connected to the asterisk too via switch. No NAT deivce between. And of course, I can call out to PSTN and also to one of the SIP clients. No problem. But when I try to call the MGCP fon from a SIP client or from outside, I get this error message. ----------------------<snip>-------------------- *CLI> Jun 20 15:30:20 NOTICE[25423]: chan_mgcp...

...bar_data = pci_readl(devfn, bar_reg); if ( (bar_data & PCI_BASE_ADDRESS_SPACE) == PCI_BASE_ADDRESS_SPACE_MEMORY ) { - resource = &mem_resource; - bar_data &= ~PCI_BASE_ADDRESS_MEM_MASK; + /* Mapping high memory if PCI deivce is 64 bits bar and the bar size + is larger than 512M */ + if (using_64bar && (bar_sz > PCI_MIN_BIG_BAR_SIZE)) { + if ( high_mem_resource.base & (bar_sz - 1) ) + high_mem_resource.base = high_mem_resource.base - +...

This object is used both by fuse_connection as well virt device. So make this object reference counted and that makes it easy to define life cycle of the object. Now deivce can be removed while filesystem is still mounted. This will cleanup all the virtqueues but virtio_fs object will still be around and will be cleaned when filesystem is unmounted and sb/fc drops its reference. Removing a device also stops all virt queues and any new reuqest gets error -ENOTCONN. Al...

...> ``` >>> >>> It seems that although they have a completion >>> queue, they are still using the ring in order. >> I guess so (at least from the above bits). Git grep -i "out of order" in >> drivers/net gives some hints. Looks like there're few deivces do this. >> >>> I guess maybe storage device may want OOO. >> Right, some iSCSI did. >> >> But tracking them elsewhere is not only for OOO. >> >> Spec said: >> >> for element address >> >> " >> In a used descriptor, El...

...> ``` >>> >>> It seems that although they have a completion >>> queue, they are still using the ring in order. >> I guess so (at least from the above bits). Git grep -i "out of order" in >> drivers/net gives some hints. Looks like there're few deivces do this. >> >>> I guess maybe storage device may want OOO. >> Right, some iSCSI did. >> >> But tracking them elsewhere is not only for OOO. >> >> Spec said: >> >> for element address >> >> " >> In a used descriptor, El...

...#nographic=0 #---------------------------------------------------------------------------- # enable stdvga, default = 0 (use cirrus logic device model) stdvga=0 #----------------------------------------------------------------------------- # serial port re-direct to pty deivce, /dev/pts/n # then xm console or minicom can connect serial=''pty'' #---------------------------------------------------------------------------- # enable ne2000, default = 0(use pcnet) ne2000=0 #---------------------------------------------------------...

Hi, Michael Tsirkin pointed out issues w.r.t various locking related TODO items and races w.r.t device removal. In this first round of cleanups, I have taken care of most pressing issues. These patches apply on top of following. git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git#virtiofs-v4 I have tested these patches with mount/umount and device removal using qemu monitor. For

...raphics, use serial port #nographic=0 #---------------------------------------------------------------------------- # enable stdvga, default = 0 (use cirrus logic device model) stdvga=0 #----------------------------------------------------------------------------- # serial port re-direct to pty deivce, /dev/pts/n # then xm console or minicom can connect serial=''pty'' #----------------------------------------------------------------------------- # enable sound card support, [sb16|es1370|all|..,..], default none #soundhw=''sb16'' #--------------------------...

...tor; > > ``` > > > > It seems that although they have a completion > > queue, they are still using the ring in order. > > I guess so (at least from the above bits). Git grep -i "out of order" in > drivers/net gives some hints. Looks like there're few deivces do this. > > > I guess maybe storage device may want OOO. > > Right, some iSCSI did. > > But tracking them elsewhere is not only for OOO. > > Spec said: > > for element address > > " > In a used descriptor, Element Address is unused. > "...