On Thu, Nov 20, 2008 at 11:17 PM, ruby <[EMAIL PROTECTED]> wrote:
> Thanks for the reply and effort of trying this out.
> would you mind spelling out the full ftrace command you used?
>
depends on what u wanti think it is better for u to fully
understand the usage and meaning of this new techn
object at
some point when you do a syscall on read.
for ext3, it will be ext3_readpage, which ask mpage_readpage() to do the
job.
what I don't follow is why the function doc right before mapge_readpage()
claims "This isn't called much at all".
These are the caller I can f
On Tue, Nov 18, 2008 at 1:06 AM, Ruby <[EMAIL PROTECTED]> wrote:
> hi, all
>
> as I understand, ->readpage() will be invoked on address space object at
> some point when you do a syscall on read.
> for ext3, it will be ext3_readpage, which ask mpage_readpage() to do the
.
> for ext3, it will be ext3_readpage, which ask mpage_readpage() to do the
> job.
>
> what I don't follow is why the function doc right before mapge_readpage()
> claims "This isn't called much at all".
>
> is this not on the primary read I/O path anymore?
>
>
> thanks
>
> Ruby
>
hi, all
as I understand, ->readpage() will be invoked on address space object at
some point when you do a syscall on read.
for ext3, it will be ext3_readpage, which ask mpage_readpage() to do the
job.
what I don't follow is why the function doc right before mapge_readpage()
claims &qu
