From: Ravish Tayal <ravish.tayal@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Kernel development list <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org,
SCSI development list <linux-scsi@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>
Subject: Re: generic_make_request fucntion for scsi_disk
Date: Sat, 20 Jun 2009 21:03:00 +0530 [thread overview]
Message-ID: <e42309110906200833q52b392d3n592712c0f81b6c9c@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0906201052090.13441-100000@netrider.rowland.org>
Sorry My mistake.
I will take care of it now onwards
regards
Ravish
On Sat, Jun 20, 2009 at 8:26 PM, Alan Stern<stern@rowland.harvard.edu> wrote:
> You should use Reply-To-All so that other people reading the mailing
> list will be able to follow and contribute to the thread.
>
> On Sat, 20 Jun 2009, Ravish Tayal wrote:
>
>> Thanks Alan,
>>
>> I am actually trying to profile the time taken by each layer to complete the
>> disk write opertaion as sys_write to queue_command invokation veries alot.
>
> Of course it varies. The kernel buffers disk writes, shuffles them
> around, and then carries them out when it wants to. As James has
> pointed out, your write(2) system calls don't directly cause any I/O to
> take place.
>
> Alan Stern
>
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-06-20 15:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e42309110906200746u441b82acvec4e3e513253af0@mail.gmail.com>
2009-06-20 14:56 ` generic_make_request fucntion for scsi_disk Alan Stern
2009-06-20 15:33 ` Ravish Tayal [this message]
2009-06-20 14:05 Ravish Tayal
2009-06-20 14:20 ` James Bottomley
[not found] ` <e42309110906200741x28595685jf56cd505d01cc795@mail.gmail.com>
2009-06-20 14:53 ` James Bottomley
[not found] ` <e42309110906200705j6a731ecay204969f639af5330-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-06-20 14:39 ` Alan Stern
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=e42309110906200833q52b392d3n592712c0f81b6c9c@mail.gmail.com \
--to=ravish.tayal@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).