Re: mmap() vs. character special file

2006-06-26 Thread Dag-Erling Smørgrav
Stanislav Sedov <[EMAIL PROTECTED]> writes: > You cannot mmap ata devices (as well as scsi ones), since mmap functions > was not implemented. This has nothing to do with ata or scsi; it's a GEOM issue. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___

Re: mmap() vs. character special file

2006-06-24 Thread Dmitry Pryanishnikov
Hello! On Sat, 24 Jun 2006, Stanislav Sedov wrote: I'm curious about mmap()ing devices (particularly, HDD slices). The manpage mentions character special files only once: You cannot mmap ata devices (as well as scsi ones), since mmap functions was not implemented. Actually, only few devices h

Re: mmap() vs. character special file

2006-06-24 Thread Peter Jeremy
On Sat, 2006-Jun-24 01:27:05 +0300, Dmitry Pryanishnikov wrote: >So it looks like one should be able to mmap() a character special file (w/o >MAP_ANON, of course). However, if I try to issue: If you have the kernel source handy, you can check which devices support mmap() by looking for a 'd_mmap'

Re: mmap() vs. character special file

2006-06-23 Thread Stanislav Sedov
On Sat, 24 Jun 2006 01:27:05 +0300 (EEST) Dmitry Pryanishnikov <[EMAIL PROTECTED]> wrote: > Hello! > > mmap(2) manpage has the following title: > > NAME > mmap -- allocate memory, or map files or devices into memory > > I'm curious about mmap()ing devices (particularly, HDD slices). The

mmap() vs. character special file

2006-06-23 Thread Dmitry Pryanishnikov
Hello! mmap(2) manpage has the following title: NAME mmap -- allocate memory, or map files or devices into memory I'm curious about mmap()ing devices (particularly, HDD slices). The manpage mentions character special files only once: [EINVAL] MAP_ANON has not been specifi