[lkml]   [2001]   [Sep]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRequest for new block_device_operations function pointer
I'd like to see if there's any issue with the inclusion of a new
function pointer for block_device_operations.

I'd like to see something like:

struct block_device_operations {
/* ... */
int (*dump) (kdev_t, char *, size_t, loff_t *);

This would allow projects such as LKCD to use a specific dump
device associated to a block device driver. This dump driver
writes data out directly to disk at a specific offset. The
reason for having it in the block_device_operations table is
to directly attach it to the lower-level disk driver rather
than going through the file_operations table. In theory, I'd
also like to see something similar for character devices, but
there is no table mechanism for this currently beyond

Then we could add our own IDE dump function pointer into ide_fops,
for example, and inevitably put our code into the IDE disk driver
without changing the rest of the driver functionality, but allowing
direct writes to the disk. The same would apply to SCSI disks.
Then all maintainers can approve the dump mechanisms before
including them into any driver release.

It would also mean that dumping wouldn't be allowed to devices
that don't have a dump function pointer, which is better than
trying to use the standard write() path for all devices.

The patch for the function pointer is the easy part, the dump
function pointer code is obviously more significant. Either
way, I can get started on those.

The arguments to dump can be different, it's the purpose that
I'm concerned with. Any other suggestion is fine ...



To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:03    [W:0.031 / U:1.172 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site