<?xml version="1.0" encoding="utf-8" ?><rss version="2.0"><channel><title><![CDATA[cl55的专栏]]></title><description><![CDATA[]]></description><link>https://blog.csdn.net/cl55</link><language>zh-cn</language><generator>https://blog.csdn.net/</generator><copyright><![CDATA[Copyright &copy; cl55]]></copyright><item><title><![CDATA[generic block layer io request processing]]></title><link>https://blog.csdn.net/cl55/article/details/64906718</link><guid>https://blog.csdn.net/cl55/article/details/64906718</guid><author>cl55</author><pubDate>Wed, 22 Mar 2017 11:34:31 +0800</pubDate><description><![CDATA[一般的基本request　queue和io scheduler的bio请求处理

standard request handling

1.
generic_make_request -> make_request_fn (blk_queue_io calls io_scheduler to merge/append the request into the associated req]]></description><category></category></item><item><title><![CDATA[multipath iscsi device attaching flow]]></title><link>https://blog.csdn.net/cl55/article/details/52513938</link><guid>https://blog.csdn.net/cl55/article/details/52513938</guid><author>cl55</author><pubDate>Mon, 12 Sep 2016 15:33:46 +0800</pubDate><description><![CDATA[1. iscsid -> login, establish connection, hand it to kernel iscsi driver
2. iscsi driver -> create /dev/ iscsi block device node, and send notification to udev
3. udevd -> compose an uevent and send]]></description><category></category></item><item><title><![CDATA["multipath -r" momentarily cause /dev/mapper/<wwid> to disappear]]></title><link>https://blog.csdn.net/cl55/article/details/52513901</link><guid>https://blog.csdn.net/cl55/article/details/52513901</guid><author>cl55</author><pubDate>Mon, 12 Sep 2016 15:24:01 +0800</pubDate><description><![CDATA["multipath -r" causes the /dev/mapper/ to disappear momentarily, which leads to some issue in consumer applications as such OpenStack. After some investigation, I found that /dev/mapper/ was deleted b]]></description><category></category></item><item><title><![CDATA[iscsi endless conn error investigation]]></title><link>https://blog.csdn.net/cl55/article/details/52513824</link><guid>https://blog.csdn.net/cl55/article/details/52513824</guid><author>cl55</author><pubDate>Mon, 12 Sep 2016 15:21:45 +0800</pubDate><description><![CDATA[symptom :
"detected conn error" error message from kernel

 "conn 0 login rejected" error messages from iscsid



investigation:
From implementation point of view, the kernel iscsi driver noti]]></description><category></category></item><item><title><![CDATA[virtio-net pci config space]]></title><link>https://blog.csdn.net/cl55/article/details/51979241</link><guid>https://blog.csdn.net/cl55/article/details/51979241</guid><author>cl55</author><pubDate>Thu, 21 Jul 2016 08:59:10 +0800</pubDate><description><![CDATA[Introduction
This article will focus on the details of virtio 1.0 device PCI config space. It will be centered around a sample virtio net PCI config taken from a real running virtual machine and expl]]></description><category></category></item><item><title><![CDATA[qemu binary path for libvirt]]></title><link>https://blog.csdn.net/cl55/article/details/51252982</link><guid>https://blog.csdn.net/cl55/article/details/51252982</guid><author>cl55</author><pubDate>Tue, 26 Apr 2016 18:42:26 +0800</pubDate><description><![CDATA[AC_PATH_PROGS([QEMU], [qemu-kvm qemu kvm qemu-system-x86_64],
                  [], [$PATH:/usr/bin:/usr/libexec])]]></description><category></category></item><item><title><![CDATA[notes on virtio-blk driver]]></title><link>https://blog.csdn.net/cl55/article/details/51000624</link><guid>https://blog.csdn.net/cl55/article/details/51000624</guid><author>cl55</author><pubDate>Mon, 28 Mar 2016 19:49:16 +0800</pubDate><description><![CDATA[from block layer perspective
not request_fn based, blk-mq based instead., thus bypassing io scheduler. using one hw queue, so mapping all per-cpu queues into that signle hw queue. requests from gener]]></description><category></category></item><item><title><![CDATA[virtio 1.0 简介]]></title><link>https://blog.csdn.net/cl55/article/details/50848268</link><guid>https://blog.csdn.net/cl55/article/details/50848268</guid><author>cl55</author><pubDate>Thu, 10 Mar 2016 17:09:19 +0800</pubDate><description><![CDATA[Introduction
This article aims to offer a different view of virtio devices from most of the other articles available online. It is neither a complete reference to the virtio 1.0 spec, nor a high-leve]]></description><category></category></item><item><title><![CDATA[cloud instance 用户配置]]></title><link>https://blog.csdn.net/cl55/article/details/50503429</link><guid>https://blog.csdn.net/cl55/article/details/50503429</guid><author>cl55</author><pubDate>Tue, 12 Jan 2016 13:12:57 +0800</pubDate><description><![CDATA[cat > userdata 
#cloud-config
password: ubuntu
chpasswd: { expire: False }
ssh_pwauth: True
EOF

sudo apt-get install kvm cloud-utils

cloud-localds userdata.img userdata


sudo kvm -hda t]]></description><category></category></item><item><title><![CDATA[numa]]></title><link>https://blog.csdn.net/cl55/article/details/50242311</link><guid>https://blog.csdn.net/cl55/article/details/50242311</guid><author>cl55</author><pubDate>Wed, 09 Dec 2015 22:05:17 +0800</pubDate><description><![CDATA[1. do_mbind


Binds the policy users specifed with a vma, so later physical memory allocation will comply with the policy, e.g. allocating memory from a certain node. Then queue_pages_range and mig]]></description><category></category></item><item><title><![CDATA[qemu numa nodes passthrough]]></title><link>https://blog.csdn.net/cl55/article/details/50207117</link><guid>https://blog.csdn.net/cl55/article/details/50207117</guid><author>cl55</author><pubDate>Mon, 07 Dec 2015 16:21:09 +0800</pubDate><description><![CDATA[有办法pass host的node到guest node去
 这个可以通过hugetlbfs
 qemu memory backend 有两种
 通常是ram_backend_memory_alloc
 有找到點了？
 另外一种是file_backend_memory_alloc
 mmap直接map到那个file上
 如果准备好hugetlbfs
 mmap就过去了
 所以说，]]></description><category></category></item><item><title><![CDATA[KVM max memory allocation]]></title><link>https://blog.csdn.net/cl55/article/details/50159525</link><guid>https://blog.csdn.net/cl55/article/details/50159525</guid><author>cl55</author><pubDate>Thu, 03 Dec 2015 13:35:47 +0800</pubDate><description><![CDATA[I did some research regarding max VM memory allocation. Finding is that the memory limitation for KVM VMs is min(mmap can give, 1T). So in general, that's going to be the amount of virtual memory mmap]]></description><category></category></item><item><title><![CDATA[KVM max vcpu allocation]]></title><link>https://blog.csdn.net/cl55/article/details/50159483</link><guid>https://blog.csdn.net/cl55/article/details/50159483</guid><author>cl55</author><pubDate>Thu, 03 Dec 2015 13:32:31 +0800</pubDate><description><![CDATA[From https://kernel.org/doc/Documentation/virtual/kvm/api.txt we can see, 


"The maximum possible value for max_vcpus can be retrieved using the 
KVM_CAP_MAX_VCPUS of the KVM_CHECK_EXTENSION ioct]]></description><category></category></item><item><title><![CDATA[x86 build IDT entry stubs]]></title><link>https://blog.csdn.net/cl55/article/details/49884289</link><guid>https://blog.csdn.net/cl55/article/details/49884289</guid><author>cl55</author><pubDate>Tue, 17 Nov 2015 10:36:26 +0800</pubDate><description><![CDATA[.section .init.rodata,"a"
ENTRY(interrupt)
.section .entry.text
.p2align 5
.p2align CONFIG_X86_L1_CACHE_SHIFT
ENTRY(irq_entries_start)
INTR_FRAME
vector=FIRST_EXTERNAL_VECTOR
.rept (NR_VECTORS]]></description><category></category></item><item><title><![CDATA[my vimrc]]></title><link>https://blog.csdn.net/cl55/article/details/49871639</link><guid>https://blog.csdn.net/cl55/article/details/49871639</guid><author>cl55</author><pubDate>Mon, 16 Nov 2015 20:55:35 +0800</pubDate><description><![CDATA[:set tags=/home/lchen/workspace/kvm/ubuntu-kernel/tags


nmap s :cs find s =expand("")
nmap g :cs find g =expand("")
nmap c :cs find c =expand("")
nmap t :cs find t =expand("")
nmap e :cs find]]></description><category></category></item><item><title><![CDATA[call_function_single_interrupt stack checking]]></title><link>https://blog.csdn.net/cl55/article/details/49824417</link><guid>https://blog.csdn.net/cl55/article/details/49824417</guid><author>cl55</author><pubDate>Fri, 13 Nov 2015 22:06:33 +0800</pubDate><description><![CDATA[The symbol call_function_single_interrupt is defined in entry_64.S, and it's an assembly routine. It will save a partial stack frame and prepare stack for the IPI irq context and call smp_call_functio]]></description><category></category></item><item><title><![CDATA[随便试试]]></title><link>https://blog.csdn.net/cl55/article/details/1667455</link><guid>https://blog.csdn.net/cl55/article/details/1667455</guid><author>cl55</author><pubDate>Tue, 26 Jun 2007 17:07:00 +0800</pubDate><description><![CDATA[试试好用否? ]]></description><category></category></item></channel></rss>