Hi,
I'm testing mmap() performance on a ramdisk. The kernel is 3.19-rc3.
The device driver is brd, and the file system is ext2. Normal mmap()
does not make sense on a ramdisk because it adds additional memory
copy, so XIP is enabled to map the pages directly into application's
address space.
Hi,
I'm testing mmap() performance on a ramdisk. The kernel is 3.19-rc3.
The device driver is brd, and the file system is ext2. Normal mmap()
does not make sense on a ramdisk because it adds additional memory
copy, so XIP is enabled to map the pages directly into application's
address space.
On Thu, Jan 30, 2014 at 2:54 PM, Randy Dunlap wrote:
> On 01/30/2014 02:17 PM, David Rientjes wrote:
>> On Thu, 30 Jan 2014, Randy Dunlap wrote:
>>
>> Hi,
>>
>> In kernel-parameters.txt, there is following description:
>>
>> memmap=nn[KMG]$ss[KMG]
>>
On Thu, Jan 30, 2014 at 11:25 AM, Randy Dunlap wrote:
> [adding linux-mm mailing list]
>
> On 01/30/2014 08:52 AM, Andiry Xu wrote:
>> Hi,
>>
>> In kernel-parameters.txt, there is following description:
>>
>> memmap=nn[KMG]$ss[KMG]
>>
Hi,
In kernel-parameters.txt, there is following description:
memmap=nn[KMG]$ss[KMG]
[KNL,ACPI] Mark specific memory as reserved.
Region of memory to be used, from ss to ss+nn.
Unfortunately this is incorrect. The meaning of nn and ss is reversed.
Hi,
In kernel-parameters.txt, there is following description:
memmap=nn[KMG]$ss[KMG]
[KNL,ACPI] Mark specific memory as reserved.
Region of memory to be used, from ss to ss+nn.
Unfortunately this is incorrect. The meaning of nn and ss is reversed.
On Thu, Jan 30, 2014 at 11:25 AM, Randy Dunlap rdun...@infradead.org wrote:
[adding linux-mm mailing list]
On 01/30/2014 08:52 AM, Andiry Xu wrote:
Hi,
In kernel-parameters.txt, there is following description:
memmap=nn[KMG]$ss[KMG]
[KNL,ACPI] Mark specific memory
On Thu, Jan 30, 2014 at 2:54 PM, Randy Dunlap rdun...@infradead.org wrote:
On 01/30/2014 02:17 PM, David Rientjes wrote:
On Thu, 30 Jan 2014, Randy Dunlap wrote:
Hi,
In kernel-parameters.txt, there is following description:
memmap=nn[KMG]$ss[KMG]
[KNL,ACPI] Mark
On Thu, Nov 7, 2013 at 2:45 PM, Andiry Xu wrote:
> On Thu, Nov 7, 2013 at 2:20 PM, Jan Kara wrote:
>> On Thu 07-11-13 13:50:09, Andiry Xu wrote:
>>> On Thu, Nov 7, 2013 at 1:07 PM, Jan Kara wrote:
>>> > On Thu 07-11-13 12:14:13, Andiry Xu wrote:
>>> >
On Thu, Nov 7, 2013 at 2:45 PM, Andiry Xu and...@gmail.com wrote:
On Thu, Nov 7, 2013 at 2:20 PM, Jan Kara j...@suse.cz wrote:
On Thu 07-11-13 13:50:09, Andiry Xu wrote:
On Thu, Nov 7, 2013 at 1:07 PM, Jan Kara j...@suse.cz wrote:
On Thu 07-11-13 12:14:13, Andiry Xu wrote:
On Wed, Nov 6
On Thu, Nov 7, 2013 at 2:20 PM, Jan Kara wrote:
> On Thu 07-11-13 13:50:09, Andiry Xu wrote:
>> On Thu, Nov 7, 2013 at 1:07 PM, Jan Kara wrote:
>> > On Thu 07-11-13 12:14:13, Andiry Xu wrote:
>> >> On Wed, Nov 6, 2013 at 1:18 PM, Jan Kara wrote:
>> >> &
On Thu, Nov 7, 2013 at 1:07 PM, Jan Kara wrote:
> On Thu 07-11-13 12:14:13, Andiry Xu wrote:
>> On Wed, Nov 6, 2013 at 1:18 PM, Jan Kara wrote:
>> > On Tue 05-11-13 17:28:35, Andiry Xu wrote:
>> >> >> Do you know the reason why write() outperforms mmap()
On Wed, Nov 6, 2013 at 1:18 PM, Jan Kara wrote:
> On Tue 05-11-13 17:28:35, Andiry Xu wrote:
>> Hi,
>>
>> On Tue, Nov 5, 2013 at 6:32 AM, Jan Kara wrote:
>> > Hello,
>> >
>> > On Mon 04-11-13 18:37:40, Andiry Xu wrote:
>> >> On M
On Wed, Nov 6, 2013 at 1:18 PM, Jan Kara j...@suse.cz wrote:
On Tue 05-11-13 17:28:35, Andiry Xu wrote:
Hi,
On Tue, Nov 5, 2013 at 6:32 AM, Jan Kara j...@suse.cz wrote:
Hello,
On Mon 04-11-13 18:37:40, Andiry Xu wrote:
On Mon, Nov 4, 2013 at 4:37 PM, Jan Kara j...@suse.cz wrote
On Thu, Nov 7, 2013 at 1:07 PM, Jan Kara j...@suse.cz wrote:
On Thu 07-11-13 12:14:13, Andiry Xu wrote:
On Wed, Nov 6, 2013 at 1:18 PM, Jan Kara j...@suse.cz wrote:
On Tue 05-11-13 17:28:35, Andiry Xu wrote:
Do you know the reason why write() outperforms mmap() in some cases? I
know it's
On Thu, Nov 7, 2013 at 2:20 PM, Jan Kara j...@suse.cz wrote:
On Thu 07-11-13 13:50:09, Andiry Xu wrote:
On Thu, Nov 7, 2013 at 1:07 PM, Jan Kara j...@suse.cz wrote:
On Thu 07-11-13 12:14:13, Andiry Xu wrote:
On Wed, Nov 6, 2013 at 1:18 PM, Jan Kara j...@suse.cz wrote:
On Tue 05-11-13 17
Hi,
On Tue, Nov 5, 2013 at 6:32 AM, Jan Kara wrote:
> Hello,
>
> On Mon 04-11-13 18:37:40, Andiry Xu wrote:
>> On Mon, Nov 4, 2013 at 4:37 PM, Jan Kara wrote:
>> > Hello,
>> >
>> > On Mon 04-11-13 14:31:34, Andiry Xu wrote:
>> >> When
Hi,
On Tue, Nov 5, 2013 at 6:32 AM, Jan Kara j...@suse.cz wrote:
Hello,
On Mon 04-11-13 18:37:40, Andiry Xu wrote:
On Mon, Nov 4, 2013 at 4:37 PM, Jan Kara j...@suse.cz wrote:
Hello,
On Mon 04-11-13 14:31:34, Andiry Xu wrote:
When I'm trying XIP on ext2, I find that xip does
Hi Jan,
On Mon, Nov 4, 2013 at 4:37 PM, Jan Kara wrote:
> Hello,
>
> On Mon 04-11-13 14:31:34, Andiry Xu wrote:
>> When I'm trying XIP on ext2, I find that xip does not work on ext2
>> with latest kernel.
>>
>> Reproduce steps:
>> Compile kernel with fol
Hi,
When I'm trying XIP on ext2, I find that xip does not work on ext2
with latest kernel.
Reproduce steps:
Compile kernel with following configs:
CONFIG_BLK_DEV_XIP=y
CONFIG_EXT2_FS_XIP=y
And run following commands:
# mke2fs -b 4096 /dev/ram0
# mount -t ext2 -o xip /dev/ram0 /mnt/ramdisk/
# dd
Hi,
When I'm trying XIP on ext2, I find that xip does not work on ext2
with latest kernel.
Reproduce steps:
Compile kernel with following configs:
CONFIG_BLK_DEV_XIP=y
CONFIG_EXT2_FS_XIP=y
And run following commands:
# mke2fs -b 4096 /dev/ram0
# mount -t ext2 -o xip /dev/ram0 /mnt/ramdisk/
# dd
Hi Jan,
On Mon, Nov 4, 2013 at 4:37 PM, Jan Kara j...@suse.cz wrote:
Hello,
On Mon 04-11-13 14:31:34, Andiry Xu wrote:
When I'm trying XIP on ext2, I find that xip does not work on ext2
with latest kernel.
Reproduce steps:
Compile kernel with following configs:
CONFIG_BLK_DEV_XIP=y
On Thu, Aug 23, 2012 at 12:53 AM, wrote:
> From: Manoj Iyer
>
> On Intel Panther Point chipset USB 3.0 devices show up as
> high-speed devices on powerup, but after an s3 cycle they are
> correctly recognized as SuperSpeed. At powerup switch the port
> to xHCI so that USB 3.0 devices are
On Thu, Aug 23, 2012 at 12:53 AM, manoj.i...@canonical.com wrote:
From: Manoj Iyer manoj.i...@canonical.com
On Intel Panther Point chipset USB 3.0 devices show up as
high-speed devices on powerup, but after an s3 cycle they are
correctly recognized as SuperSpeed. At powerup switch the port
solution than your original patch.
Thanks,
Andiry
>
> On Tue, 21 Aug 2012, Andiry Xu wrote:
>
>> On Tue, Aug 21, 2012 at 12:06 PM, wrote:
>>>
>>> From: Manoj Iyer
>>>
>>> USB 3.0 devices show up as high-speed devices on powerup, after an
On Tue, Aug 21, 2012 at 12:06 PM, wrote:
> From: Manoj Iyer
>
> USB 3.0 devices show up as high-speed devices on powerup, after an
> s3 cycle they are correctly recognized as SuperSpeed. At powerup
> unconditionally switch the port to xHCI like we do when we resume
> from suspend.
>
> BugLink:
solution than your original patch.
Thanks,
Andiry
On Tue, 21 Aug 2012, Andiry Xu wrote:
On Tue, Aug 21, 2012 at 12:06 PM, manoj.i...@canonical.com wrote:
From: Manoj Iyer manoj.i...@canonical.com
USB 3.0 devices show up as high-speed devices on powerup, after an
s3 cycle they are correctly
On Tue, Aug 21, 2012 at 12:06 PM, manoj.i...@canonical.com wrote:
From: Manoj Iyer manoj.i...@canonical.com
USB 3.0 devices show up as high-speed devices on powerup, after an
s3 cycle they are correctly recognized as SuperSpeed. At powerup
unconditionally switch the port to xHCI like we do
201 - 228 of 228 matches
Mail list logo