search for: subsys_nam

On Thu, Nov 19, 2015 at 04:21:03PM -0800, Ming Lin wrote: > #define NVMET_SUBSYS_NAME_LEN 256 > char subsys_name[NVMET_SUBSYS_NAME_LEN]; > + > + void *opaque; > + void (*start)(void *); > }; Why can't vhost use container_of to get at the containing structure similar to what the loop driver does? In addition I think we'll eventually need an ops str...

...libvirt-1.0.6-1_WR4.3.x86_64_XXX.2.x86_64 > > Problem : > > # virsh cpu-stats CLA-0 > error: Failed to retrieve CPU statistics for domain 'CLA-0' > *error: internal error error accessing cgroup cpuacct for vcpu* > > Related info : > > # cat /proc/cgroups > #subsys_name hierarchy num_cgroups enabled > cpuset 3 4 1 > ns 0 1 1 > cpu 1 6 1 > cpuacct...

...ur linux machine. After this upgrade "virsh cpu-stats <domain>" command is not working on our HardWare. *virsh # cpu-stats test error: Failed to retrieve CPU statistics for domain 'test' error: internal error error accessing cgroup cpuacct for vcpu* ** *# cat /proc/cgroups #subsys_name hierarchy num_cgroups enabled cpuset 3 4 1 ns 0 1 1 cpu 1 6 1 cpuacct 7 3 1 memory 2 3 1 freezer 0 1 1 net_cls 0 1 1 blkio 0 1 1 * *# chkconfig --list | grep cg cgroups_mount...

...U statistics for domain 'CLA-0' > >> *error: internal error error accessing cgroup cpuacct for vcpu* > > Are you sure cpuacct was mounted prior to libvirtd starting? > > >> > >> Related info : > >> > >> # cat /proc/cgroups > >> #subsys_name hierarchy num_cgroups enabled > >> cpuset 3 4 1 > >> ns 0 1 1 > >> cpu 1 6...

...static void nvmet_clear_ctrl(struct nvmet_ctrl *ctrl) diff --git a/drivers/nvme/target/nvmet.h b/drivers/nvme/target/nvmet.h index 9335584..eac008b 100644 --- a/drivers/nvme/target/nvmet.h +++ b/drivers/nvme/target/nvmet.h @@ -59,6 +59,9 @@ struct nvmet_ctrl { struct kref ref; #define NVMET_SUBSYS_NAME_LEN 256 char subsys_name[NVMET_SUBSYS_NAME_LEN]; + + void *opaque; + void (*start)(void *); }; struct nvmet_subsys { -- 1.9.1

...cting some issue in virsh when it is trying to find to where that cgroups is mounted in a system (default in ubuntu is /sys/fs/cgroup/cpuset/libvirt/, but in our platform uses /dev/cgroup_xxx). Find /proc/cgroups and /proc/mounts log below: ================================== # cat /proc/cgroups #subsys_name hierarchy num_cgroups enabled cpuset 0 1 1 ns 0 1 1 cpu 1 3 1 cpuacct 0 1 1 memory 2 1 1 freezer 0 1 1 net_cls 0 1 1 blkio 0 1 1 # cat /proc/mounts cpu /dev/cgroup_cpu cgroup...

...ot;virsh cpu-stats <domain>" command > is not working on our HardWare. > > *virsh # cpu-stats test > error: Failed to retrieve CPU statistics for domain 'test' > error: internal error error accessing cgroup cpuacct for vcpu* > ** > *# cat /proc/cgroups > #subsys_name hierarchy num_cgroups enabled > cpuset 3 4 1 > ns 0 1 1 > cpu 1 6 1 > cpuacct 7 3 1 > memory 2 3 1 > freezer 0 1 1 > net_cls 0 1 1 > blkio 0 1 1 > *...

...CLA-0 >> error: Failed to retrieve CPU statistics for domain 'CLA-0' >> *error: internal error error accessing cgroup cpuacct for vcpu* Are you sure cpuacct was mounted prior to libvirtd starting? >> >> Related info : >> >> # cat /proc/cgroups >> #subsys_name hierarchy num_cgroups enabled >> cpuset 3 4 1 >> ns 0 1 1 >> cpu 1 6 1 >> cpu...

...} } # create this group in the controllers cpu { } cpuset { } memory { } devices { } freezer { } net_cls { } blkio { } } - /etc/cgrules is deafult one, so everything is commented. Maybe shall I edit a line ?? - gabx@hortensia ➤➤ ~ # cat /proc/cgroups #subsys_name hierarchy num_cgroups enabled cpuset 3 5 1 cpu 4 4 1 cpuacct 4 4 1 memory 5 5 1 devices 6 4 1 freezer 7 5 1 net_cls 8 5 1 blkio 9 4 1 Something puzzles me. In /sys/fs/cgroup/blkio, I see two dirs: dahlia and machine...

...xec,relatime,net_prio,net_cls 0 0 cgroup /sys/fs/cgroup/perf_event cgroup rw,nosuid,nodev,noexec,relatime,perf_event 0 0 cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0 cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0 $ cat /proc/cgroups #subsys_name hierarchy num_cgroups enabled cpuset 6 1 1 cpu 7 1 1 cpuacct 7 1 1 memory 11 1 1 devices 2 1 1 freezer 5 1 1 net_cls 8 1 1 blkio 10 1 1 perf_event 9 1 1 hugetlb 3...

...command > > is not working on our HardWare. > > > > *virsh # cpu-stats test > > error: Failed to retrieve CPU statistics for domain 'test' > > error: internal error error accessing cgroup cpuacct for vcpu* > > ** > > *# cat /proc/cgroups > > #subsys_name hierarchy num_cgroups enabled > > cpuset 3 4 1 > > ns 0 1 1 > > cpu 1 6 1 > > cpuacct 7 3 1 > > memory 2 3 1 > > freezer 0 1 1 > > net_cls 0 1 1 &gt...

Hi, This is the first attempt to add a new qemu nvme backend using in-kernel nvme target. Most code are ported from qemu-nvme and also borrow code from Hannes Reinecke's rts-megasas. It's similar as vhost-scsi, but doesn't use virtio. The advantage is guest can run unmodified NVMe driver. So guest can be any OS that has a NVMe driver. The goal is to get as good performance as

Hi, This is the first attempt to add a new qemu nvme backend using in-kernel nvme target. Most code are ported from qemu-nvme and also borrow code from Hannes Reinecke's rts-megasas. It's similar as vhost-scsi, but doesn't use virtio. The advantage is guest can run unmodified NVMe driver. So guest can be any OS that has a NVMe driver. The goal is to get as good performance as