All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carsten Otte <cotte@freenet.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	schwidefsky@de.ibm.com, akpm@osdl.org
Subject: Re: [RFC/PATCH 1/5] bdev: execute in place (V2)
Date: Wed, 18 May 2005 17:36:49 +0200	[thread overview]
Message-ID: <428B6111.3000802@freenet.de> (raw)
In-Reply-To: <20050518142739.GB23162@infradead.org>

Christoph Hellwig wrote:

>>+	int (*direct_access) (struct inode *, sector_t, unsigned long *);
>>    
>>
>
>this should have a block_device * first argument.
>  
>
While I agree that (block_device *) would be a good thing to address
the target block device, the inode *  is consistent with other
operations in this vector: open, release, & ioctl use the same scheme.
The reason for inode * here is that the caller has no easy way to get
to the block_device *. How would the filesystem do that?

  reply	other threads:[~2005-05-18 15:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1116422644.2202.1.camel@cotte.boeblingen.de.ibm.com>
2005-05-18 13:53 ` [RFC/PATCH 1/5] bdev: execute in place (V2) Carsten Otte
2005-05-18 14:27   ` Christoph Hellwig
2005-05-18 15:36     ` Carsten Otte [this message]
2005-05-18 15:37       ` Christoph Hellwig
2005-05-18 13:53 ` [RFC/PATCH 2/5] mm/fs: " Carsten Otte
2005-05-18 14:27   ` Christoph Hellwig
2005-05-18 14:56     ` Carsten Otte
2005-05-18 15:00       ` Christoph Hellwig
2005-05-18 15:31         ` Carsten Otte
2005-05-18 15:36           ` Christoph Hellwig
2005-05-18 15:50             ` Carsten Otte
2005-05-18 15:53               ` Christoph Hellwig
2005-05-18 13:53 ` [RFC/PATCH 3/5] ext2: " Carsten Otte
2005-05-18 13:53 ` [RFC/PATCH 4/5] loop: " Carsten Otte
2005-05-18 14:28   ` Christoph Hellwig
2005-05-18 14:38     ` Carsten Otte
2005-05-18 13:54 ` [RFC/PATCH 5/5] madvice/fadvice: " Carsten Otte

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=428B6111.3000802@freenet.de \
    --to=cotte@freenet.de \
    --cc=akpm@osdl.org \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schwidefsky@de.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.