Re: Using DMA in read/write, setting block size for I/O -> max_sectors

Arjan van de Ven wrote:

no it's a property of the hardware and as such the DRIVER has to set it.
Not all hw can deal with really big sizes, so the driver is supposed to
set what the hw is capable of.

so I need to send some ioctl to the driver to set the transfer size orfind something in the /proc/scsi area, isn't it?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- Using DMA in read/write, setting block size for I/O
  - From: Karthik Sarangan <[email protected]>
- Re: Using DMA in read/write, setting block size for I/O
  - From: Arjan van de Ven <[email protected]>
- Re: Using DMA in read/write, setting block size for I/O
  - From: Arjan van de Ven <[email protected]>
- Re: Using DMA in read/write, setting block size for I/O -> max_sectors
  - From: Karthik Sarangan <[email protected]>
- Re: Using DMA in read/write, setting block size for I/O -> max_sectors
  - From: Arjan van de Ven <[email protected]>

Prev by Date: Issues in Booting kernel 2.6.13
Next by Date: Re: [Question]: system register cr3
Previous by thread: Re: Using DMA in read/write, setting block size for I/O -> max_sectors
Next by thread: Re: Using DMA in read/write, setting block size for I/O
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]