From: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
To: Mikulas Patocka <mpatocka@redhat.com>,
"xinhui.pan" <xinhuix.pan@intel.com>,
linux-kernel@vger.kernel.org, agk@redhat.com, snitzer@redhat.com,
dm-devel@redhat.com, "Liu, ShuoX" <shuox.liu@intel.com>
Subject: Re: [dm-devel] [PATCH] md/dm-ioctl.c: optimize memory allocation in copy_params
Date: Wed, 23 Jul 2014 11:06:26 +0800 [thread overview]
Message-ID: <53CF26B2.6060503@linux.intel.com> (raw)
In-Reply-To: <20140722012352.GD6822@agk-dp.fab.redhat.com>
On 2014/7/22 9:23, Alasdair G Kergon wrote:
>>>> On 2014/7/9 6:39, Mikulas Patocka wrote:
>>> Which ioctl with more than 16kB
>>> arguments do you use?
> Unanswered. Let's ask the same question in a different way:
>
> Please supply the output of these three commands on the real-world system on
> which you believe that that particular allocation is causing you a problem:
> dmsetup info -c
> dmsetup table
> dmsetup status
Android doesn't include the command. We compiled lvm2-2_02_107.tar.gz and copy
dmsetup to the board. But command reports No devices.
# /data/bin/dmsetup info
No devices found
# cat /proc/devices
Character devices:
1 mem
4 /dev/vc/0
4 tty
4 ttyS
4 ttyMFD
5 /dev/tty
5 /dev/console
5 /dev/ptmx
7 vcs
10 misc
13 input
21 sg
29 fb
81 video4linux
89 i2c
108 ppp
116 alsa
128 ptm
136 pts
153 spi
166 ttyACM
180 usb
188 ttyUSB
189 usb_device
202 cpu/msr
203 cpu/cpuid
226 drm
241 mdm_ctrl
242 sep54
243 roccat
244 hidraw
245 ttyGS
246 usbmon
247 ttyPTI
248 gsmtty
249 bsg
250 iio
251 ptp
252 pps
253 media
254 rtc
Block devices:
1 ramdisk
259 blkext
7 loop
8 sd
9 md
11 sr
65 sd
66 sd
67 sd
68 sd
69 sd
70 sd
71 sd
128 sd
129 sd
130 sd
131 sd
132 sd
133 sd
134 sd
135 sd
179 mmc
253 device-mapper
254 mdp
next prev parent reply other threads:[~2014-07-23 3:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 10:22 [PATCH] md/dm-ioctl.c: optimize memory allocation in copy_params xinhui.pan
2014-07-08 22:39 ` [dm-devel] " Mikulas Patocka
2014-07-09 2:01 ` Zhang, Yanmin
2014-07-09 3:37 ` xinhui.pan
2014-07-09 14:53 ` Mikulas Patocka
2014-07-22 1:02 ` Zhang, Yanmin
2014-07-22 1:23 ` Alasdair G Kergon
2014-07-22 2:04 ` Alasdair G Kergon
2014-07-23 3:15 ` Zhang, Yanmin
2014-07-23 3:06 ` Zhang, Yanmin [this message]
2014-07-23 12:16 ` Mikulas Patocka
2014-07-23 12:54 ` Alasdair G Kergon
2014-07-23 17:14 ` Mikulas Patocka
2014-07-24 5:53 ` Zhang, Yanmin
2014-07-23 12:39 ` Mikulas Patocka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53CF26B2.6060503@linux.intel.com \
--to=yanmin_zhang@linux.intel.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=shuox.liu@intel.com \
--cc=snitzer@redhat.com \
--cc=xinhuix.pan@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).