search for: yoshikawa

...do that. */ 3a4d5c94e95935 Michael S. Tsirkin 2010-01-14 1550 if (vq->private_data) { 3a4d5c94e95935 Michael S. Tsirkin 2010-01-14 1551 r = -EBUSY; 3a4d5c94e95935 Michael S. Tsirkin 2010-01-14 1552 break; 3a4d5c94e95935 Michael S. Tsirkin 2010-01-14 1553 } 7ad9c9d2704854 Takuya Yoshikawa 2010-05-27 1554 if (copy_from_user(&s, argp, sizeof s)) { 7ad9c9d2704854 Takuya Yoshikawa 2010-05-27 1555 r = -EFAULT; 3a4d5c94e95935 Michael S. Tsirkin 2010-01-14 1556 break; 7ad9c9d2704854 Takuya Yoshikawa 2010-05-27 1557 } 3a4d5c94e95935 Michael S. Tsirkin 2010-01-14...

We try to keep the defconfig untouched after decoupling CONFIG_VHOST out of CONFIG_VIRTUALIZATION in commit 20c384f1ea1a ("vhost: refine vhost and vringh kconfig") by enabling VHOST_MENU by default. Then the defconfigs can keep enabling CONFIG_VHOST_NET without the caring of CONFIG_VHOST. But this will leave a "CONFIG_VHOST_MENU=y" in all defconfigs and even for the ones that

We try to keep the defconfig untouched after decoupling CONFIG_VHOST out of CONFIG_VIRTUALIZATION in commit 20c384f1ea1a ("vhost: refine vhost and vringh kconfig") by enabling VHOST_MENU by default. Then the defconfigs can keep enabling CONFIG_VHOST_NET without the caring of CONFIG_VHOST. But this will leave a "CONFIG_VHOST_MENU=y" in all defconfigs and even for the ones that

...erstanding, the mm_struct of a thread is same as its parent's. So, even if we attach the TIDs of some threads to different cgroups the tracking always returns the same bio_cgroup -- its parent's group. Do you have some policy about in which case we can use your tracking? Thanks, -- Takuya Yoshikawa

...erstanding, the mm_struct of a thread is same as its parent's. So, even if we attach the TIDs of some threads to different cgroups the tracking always returns the same bio_cgroup -- its parent's group. Do you have some policy about in which case we can use your tracking? Thanks, -- Takuya Yoshikawa

Hello, I have summarized the topics for the IO controller mini-summit and written the ideas seen in the mailing list. - The place where IO controller should be implemented - Block layer in conjunction with the IO scheduler - Common layer right above the IO scheduler - CFQ enhancement. - Both block and common layer, users can select whichever controller they want. - VFS layer -

Hello, I have summarized the topics for the IO controller mini-summit and written the ideas seen in the mailing list. - The place where IO controller should be implemented - Block layer in conjunction with the IO scheduler - Common layer right above the IO scheduler - CFQ enhancement. - Both block and common layer, users can select whichever controller they want. - VFS layer -

Hello, I have summarized the topics for the IO controller mini-summit and written the ideas seen in the mailing list. - The place where IO controller should be implemented - Block layer in conjunction with the IO scheduler - Common layer right above the IO scheduler - CFQ enhancement. - Both block and common layer, users can select whichever controller they want. - VFS layer -

...ght adding ioprio to blktrace output might be helpful. Implementation: 1. I used req_get_ioprio() and [new]bio_get_ioprio() to get ioprio. Currently bio_get_ioprio just returns current->io_context->ioprio. Appreciate any comments: Does this kind of information helpful? Thanks, Takuya Yoshikawa Example: 8,16 0 1 0.000000000 2664 Q R ioprio=16386 81920 + 8 [tiotest] 8,16 0 2 0.000010493 2664 G R ioprio=16386 81920 + 8 [tiotest] 8,16 0 3 0.000013217 2664 P N ioprio= 0 [tiotest] 8,16 0 4 0.000014164 2664 I...

Hi All, I have got excellent results of dm-ioband, that controls the disk I/O bandwidth even when it accepts delayed write requests. In this time, I ran some benchmarks with a high-end storage. The reason was to avoid a performance bottleneck due to mechanical factors such as seek time. You can see the details of the benchmarks at: http://people.valinux.co.jp/~ryov/dm-ioband/hps/ Thanks, Ryo

Hi All, I have got excellent results of dm-ioband, that controls the disk I/O bandwidth even when it accepts delayed write requests. In this time, I ran some benchmarks with a high-end storage. The reason was to avoid a performance bottleneck due to mechanical factors such as seek time. You can see the details of the benchmarks at: http://people.valinux.co.jp/~ryov/dm-ioband/hps/ Thanks, Ryo

Hi All, I have got excellent results of dm-ioband, that controls the disk I/O bandwidth even when it accepts delayed write requests. In this time, I ran some benchmarks with a high-end storage. The reason was to avoid a performance bottleneck due to mechanical factors such as seek time. You can see the details of the benchmarks at: http://people.valinux.co.jp/~ryov/dm-ioband/hps/ Thanks, Ryo

Hi everyone, This series of patches of dm-ioband now includes "The bio tracking mechanism," which has been posted individually to this mailing list. This makes it easy for anybody to control the I/O bandwidth even when the I/O is one of delayed-write requests. Have fun! This series of patches consists of two parts: 1. dm-ioband Dm-ioband is an I/O bandwidth controller implemented

Hi everyone, This series of patches of dm-ioband now includes "The bio tracking mechanism," which has been posted individually to this mailing list. This makes it easy for anybody to control the I/O bandwidth even when the I/O is one of delayed-write requests. Have fun! This series of patches consists of two parts: 1. dm-ioband Dm-ioband is an I/O bandwidth controller implemented

Hi everyone, This series of patches of dm-ioband now includes "The bio tracking mechanism," which has been posted individually to this mailing list. This makes it easy for anybody to control the I/O bandwidth even when the I/O is one of delayed-write requests. Have fun! This series of patches consists of two parts: 1. dm-ioband Dm-ioband is an I/O bandwidth controller implemented

...Takahisa Tanaka <mc74hc00@gmail.com> Takamori Yamaguchi <takamori.yamaguchi@jp.sony.com> Takashi Iwai <tiwai@suse.de> Takashi Yoshii <takashi.yoshii.zj@renesas.com> Taku Izumi <izumi.taku@jp.fujitsu.com> Taku Izumi <izumim.taku@jp.fujitsu.com> Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp> Takuya Yoshikawa <yoshikawa_takuya_b1@lab.ntt.co.jp> Tamas K Lengyel <tamas.lengyel@zentific.com> Tammy Yang <tammy.yang@canonical.com> Tang Chen <tangchen@cn.fujitsu.com> Tang Liang <liang.tang@oracle.com> Tang Yuanti...

...Takahisa Tanaka <mc74hc00@gmail.com> Takamori Yamaguchi <takamori.yamaguchi@jp.sony.com> Takashi Iwai <tiwai@suse.de> Takashi Yoshii <takashi.yoshii.zj@renesas.com> Taku Izumi <izumi.taku@jp.fujitsu.com> Taku Izumi <izumim.taku@jp.fujitsu.com> Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp> Takuya Yoshikawa <yoshikawa_takuya_b1@lab.ntt.co.jp> Tamas K Lengyel <tamas.lengyel@zentific.com> Tammy Yang <tammy.yang@canonical.com> Tang Chen <tangchen@cn.fujitsu.com> Tang Liang <liang.tang@oracle.com> Tang Yuanti...

...Takahisa Tanaka <mc74hc00@gmail.com> Takamori Yamaguchi <takamori.yamaguchi@jp.sony.com> Takashi Iwai <tiwai@suse.de> Takashi Yoshii <takashi.yoshii.zj@renesas.com> Taku Izumi <izumi.taku@jp.fujitsu.com> Taku Izumi <izumim.taku@jp.fujitsu.com> Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp> Takuya Yoshikawa <yoshikawa_takuya_b1@lab.ntt.co.jp> Tamas K Lengyel <tamas.lengyel@zentific.com> Tammy Yang <tammy.yang@canonical.com> Tang Chen <tangchen@cn.fujitsu.com> Tang Liang <liang.tang@oracle.com> Tang Yuanti...

...int from the prompt this will work. But I can't get the windows machines to print. They see it and will install drivers but that is as far as it goes. Know it something that I am or am not doing can anyone point me in the right direction. Robert Lee relee1950@yahoo.com Return-Path: <YoshikawaS@o-works.co.jp> Delivered-To: samba@samba.org Received: from fixer2.sega.co.jp (fixer2.sega.co.jp [157.109.66.3]) by lists.samba.org (Postfix) with ESMTP id D1EA24E32 for <samba@samba.org>; Wed, 11 Jul 2001 07:15:38 -0700 (PDT) Received: from keeper.sega.co.jp (keeper [157.109.65.6]) b...

...Takahisa Tanaka <mc74hc00@gmail.com> Takamori Yamaguchi <takamori.yamaguchi@jp.sony.com> Takashi Iwai <tiwai@suse.de> Takashi Yoshii <takashi.yoshii.zj@renesas.com> Taku Izumi <izumi.taku@jp.fujitsu.com> Taku Izumi <izumim.taku@jp.fujitsu.com> Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp> Takuya Yoshikawa <yoshikawa_takuya_b1@lab.ntt.co.jp> Tamas K Lengyel <tamas.lengyel@zentific.com> Tammy Yang <tammy.yang@canonical.com> Tang Chen <tangchen@cn.fujitsu.com> Tang Liang <liang.tang@oracle.com> Tang Yuanti...