search for: 256kib

On May 25, 2014 3:39 AM, "Geert Stappers" <stappers at stappers.nl> wrote: > > > While going throug old posts found: > > Op 2013-08-31 om 17:01 schreef Raphael S.Carvalho: > > Calc the size of ldlinux.sys from ldlinux.bin, and check if it exceeds the limit. > > ldlinux.sys must fit between the bootsector and two copies of ADV whose size may vary. >

...Paulo: does UFS2 have a hard 64kiB limit? I know it's not > installed to the first sector where the first superblock is located. I have no much experience with UFS2 filesystem. I've just took a quick look at its internals and I can see that UFS2 places its superblock at either 64KiB or 256KiB (depending on the media being used). I haven't found any code that tries to read superblock from 256KiB, but I'm not sure if we can rely on it being always at 64KiB. >> IMNSHO is including core/ldlinux_limit.pl better >> than waiting for a better core/ldlinux_limit.pl > &gt...

I was getting a order 4 allocation failure from kmalloc when testing some game after a few days uptime with some suspend/resumes. For big allocations vmalloc should be used instead. Also limit size more aggressively to 256 KiB. Signed-off-by: Maarten Lankhorst <maarten.lankhorst at canonical.com> --- drivers/gpu/drm/nouveau/nouveau_gem.c | 30 +++++++++++++++++++++++------- 1 file

[This email is either empty or too large to be displayed at this time]

Hi everyone, I have been studing the VM code in order to come with a better implementation of my fix for large pages usage on GK20A (https://lkml.org/lkml/2014/6/3/375 ). Following some older threads about this code (http://marc.info/?l=dri-devel&m=137618326022935 ) also left me kind of puzzled, and I wonder if we could not simplify and improve things there. It seems like arbitrary

...hysical id: 2 slot: L1-Cache size: 64KiB capacity: 64KiB capabilities: synchronous internal write-through data *-cache:1 description: L2 cache physical id: 3 slot: L2-Cache size: 256KiB capacity: 256KiB capabilities: synchronous internal write-through data *-cache:2 description: L3 cache physical id: 4 slot: L3-Cache size: 3MiB capacity: 3MiB capabilities: synch...

...And on the subject of the NV storage... does -pflash work on qemu-xen, as long as we''re not actually running *code* from the device and we''re only using it for data storage? Are you content with my stated plan to provide a "disk" image for that, which is something like a 256KiB file on the host side, exposed as a flash device to the guest? -- dwmw2 ¹ Statements that refer to plans and expectations for the year and the future are forward-looking statements that involve a number of risks and uncertainties. Words such as “anticipates,” “expects,” “intends,” “plans,”...

...ld be used instead. I've picked up this patch with a minor modification (see below) > > Also limit size more aggressively to 256 KiB. I dropped this, it's *completely* useless, the sizes are already enforced right at the beginning of the ioctl (shockingly, the max size is going to be 256KiB already)... Thanks, Ben. > > Signed-off-by: Maarten Lankhorst <maarten.lankhorst at canonical.com> > --- > drivers/gpu/drm/nouveau/nouveau_gem.c | 30 +++++++++++++++++++++++------- > 1 file changed, 23 insertions(+), 7 deletions(-) > > diff --git a/drivers/gpu/drm/nou...

...K drive >ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 >ACPI: PCI Interrupt 0000:00:04.0[A] -> GSI 32 (level, low) -> IRQ 57 >eth0: RTL-8139C+ at 0xc8814000, 00:16:3e:71:56:22, IRQ 57 >8139too Fast Ethernet driver 0.9.27 >hda: max request size: 512KiB >hda: 6144000 sectors (3145 MB) w/256KiB Cache, CHS=6095/255/63, (U)DMA >hda: lost interrupt >hda: lost interrupt >hda: lost interrupt >hda: set_multmode: status=0x41 { DriveReady Error } >hda: set_multmode: error=0x04 { DriveStatusError} >ide: failed opceode was: 0xef >hda: lost interrupt >hda: lost interrupt >...

...to chunk things up at one size, but ends up having to backfill things dynamically. the client is able to recover though, so that's good. when doing a write of a really large size, OpenSSH will just close the connection as soon as it sees the header with the large write. the server hardcodes 256KiB (SFTP_MAX_MSG_LENGTH) and any attempt to write anything larger than that is immediately rejected. this is not friendly and clients basically have to default to 32KiB all the time and force users to manually select a size that they happen to know the server they're connecting to supports. if t...

I can't seem to get the read and write performance better than approximately 40MB/s on an ext2 file system. IMO, this is horrible performance for a 6-drive, hardware RAID 5 array. Please have a look at what I'm doing and let me know if anybody has any suggestions on how to improve the performance... System specs: ----------------- 2 x 2.8GHz Xeons 6GB RAM 1 3ware 9500S-12 2 x 6-drive,

...ttings: hdc:pio, hdd:pio Probing IDE interface ide0... hda: QEMU HARDDISK, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Probing IDE interface ide1... hdc: QEMU DVD-ROM, ATAPI CD/DVD-ROM drive ide1 at 0x170-0x177,0x376 on irq 15 hda: max request size: 512KiB hda: 104854328 sectors (53685 MB) w/256KiB Cache, CHS=16383/255/63, (U)DMA hda: cache flushes supported hda: hda1 hda2 ....<SNIP>...... Xen version 3.3. Hypercall area is 1 pages. Grant table initialized parport: PnPBIOS parport detected. parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE] piix4_smbus 0000:00:01.3: Found 0000:00:01.3...

Hi , Can any one please let me know how to capture all the boot messages of the Guest OS into a text file? I do xm create -c /etc/xen/hvm.cfg to boot the guest OS. Thanks Kishore _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...e1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:pio, hdd:pio hda: QEMU HARDDISK, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 hdc: QEMU DVD-ROM, ATAPI CD/DVD-ROM drive ide1 at 0x170-0x177,0x376 on irq 15 (XEN) PCI add device 00:01.1 hda: max request size: 512KiB hda: 204800 sectors (104 MB) w/256KiB Cache, CHS=203/255/63, (U)DMA hda: cache flushes supported  hda: unknown partition table hdc: ATAPI 4X CD-ROM drive, 512kB Cache, (U)DMA Uniform CD-ROM driver Revision: 3.20 Adaptec aacraid driver (1.1-5[2409]-mh2) 3ware Storage Controller device driver for Linux v1.26.02.001. Fusion MPT base drive...

...e1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:pio, hdd:pio hda: QEMU HARDDISK, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 hdc: QEMU DVD-ROM, ATAPI CD/DVD-ROM drive ide1 at 0x170-0x177,0x376 on irq 15 (XEN) PCI add device 00:01.1 hda: max request size: 512KiB hda: 204800 sectors (104 MB) w/256KiB Cache, CHS=203/255/63, (U)DMA hda: cache flushes supported  hda: unknown partition table hdc: ATAPI 4X CD-ROM drive, 512kB Cache, (U)DMA Uniform CD-ROM driver Revision: 3.20 Adaptec aacraid driver (1.1-5[2409]-mh2) 3ware Storage Controller device driver for Linux v1.26.02.001. Fusion MPT base drive...

I recently bought 2 different USB flash disks. These are some cheap no-name devices. Their parameters: bytes C/H/S ID 4194304512 509/255/63 Vendor: Generic Model: USB Flash Drive Rev: 1.00 ANSI SCSI revision: 02 4288676352 1023/132/62 Vendor: USB Model: USB 2.0 Rev: 1.00 ANSI SCSI revision: 02 When I put a FAT32 filesystem on them,

Hi, My xen guest stopped booting suddenly and giving me the below error message. Any idea what is going wrong here? DOM 0 boots OK though. ata5.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 ata5.00: irq_stat 0x40000008 ata5.00: failed command: READ FPDMA QUEUED ata5.00: cmd 60/00:00:cd:ee:36/02:00:09:00:00/40 tag 0 ncq 262144 in res 51/40:72:5b:f0:36/d9:00:09:00:00/40 Emask

Hi, My xen guest stopped booting suddenly and giving me the below error message. Any idea what is going wrong here? DOM 0 boots OK though. ata5.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 ata5.00: irq_stat 0x40000008 ata5.00: failed command: READ FPDMA QUEUED ata5.00: cmd 60/00:00:cd:ee:36/02:00:09:00:00/40 tag 0 ncq 262144 in res 51/40:72:5b:f0:36/d9:00:09:00:00/40 Emask