From: Boaz Harrosh <bharrosh@panasas.com>
To: <tao.peng@emc.com>
Cc: <Trond.Myklebust@netapp.com>, <bergwolf@gmail.com>,
<linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 1/3] NFS41: add pnfs_dio_begin/dio_end
Date: Mon, 28 May 2012 13:51:54 +0300 [thread overview]
Message-ID: <4FC358CA.2090301@panasas.com> (raw)
In-Reply-To: <4FC356FA.2070008@panasas.com>
On 05/28/2012 01:44 PM, Boaz Harrosh wrote:
> On 05/28/2012 07:13 AM, tao.peng@emc.com wrote:
>
>>> -----Original Message-----
>>> From: Myklebust, Trond [mailto:Trond.Myklebust@netapp.com]
>>> Sent: Monday, May 28, 2012 11:43 AM
>>> To: Peng, Tao
>>> Cc: bergwolf@gmail.com; linux-nfs@vger.kernel.org
>>> Subject: RE: [PATCH 1/3] NFS41: add pnfs_dio_begin/dio_end
>>>
>>> On Sun, 2012-05-27 at 22:30 -0400, tao.peng@emc.com wrote:
>>>> I'm afraid there is. There is no way to pass struct blk_plug around pg_init/pg_doio, unless we put
>>> it in struct nfs_pageio_descriptor, which I think is more intrusive and less efficient as it is only
>>> useful for block layout driver in DIO case.
>>>
>>> Then add a 'void *pg_layout_private' field to nfs_pageio_descriptor and
>>> allocate the struct blk_plug dynamically.
>>>
>
>> OK. I thought data structure change is more intrusive because it
>> affects all layout drivers and generic NFS as well. But since you
>> think it is OK, I will change it as you suggested.
>>
>
>
> I want a pg_layout_private in nfs_pageio_descriptor as well. I even wrote
> the ML about it. And everyone agreed. (Just never had time to finish)
>
> So yes please do add it. it will have more users.
>
I forgot to say. You might want/need to pass this pg_layout_private
back to LD->paglist_write/read. (If you need to, I will)
(In fact one optimization I wanted for a long time is to pass
nfs_pageio_descriptor to paglist_write/read directly instead of
duplicating all it's members (back and forth). In a new invented
structures where the worse is that the common code of read and write
can't be common because it is not the same types.
But that's for another patch)
Ciao
Boaz
>
>> Thanks,
>> Tao
>>
>
>
> Thanks
> Boaz
next prev parent reply other threads:[~2012-05-28 10:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-27 5:32 [PATCH 0/3] NFS41: make block layout driver work w/ NFS DIO changes Peng Tao
2012-05-27 5:32 ` [PATCH 1/3] NFS41: add pnfs_dio_begin/dio_end Peng Tao
2012-05-27 16:29 ` Myklebust, Trond
2012-05-28 2:30 ` tao.peng
2012-05-28 3:42 ` Myklebust, Trond
2012-05-28 4:13 ` tao.peng
2012-05-28 10:44 ` Boaz Harrosh
2012-05-28 10:51 ` Boaz Harrosh [this message]
2012-05-28 17:14 ` Peng Tao
2012-05-28 17:24 ` Boaz Harrosh
2012-05-28 17:36 ` Peng Tao
2012-05-28 17:44 ` Myklebust, Trond
2012-05-27 5:32 ` [PATCH 2/3] pnfsblock: call block plug in bl_dio_begin/end Peng Tao
2012-05-27 5:33 ` [PATCH 3/3] pnfsblock: bail out unaligned DIO Peng Tao
2012-05-27 16:38 ` Myklebust, Trond
2012-05-28 2:30 ` tao.peng
2012-05-28 3:45 ` Myklebust, Trond
2012-05-28 4:26 ` tao.peng
2012-05-28 16:33 ` Myklebust, Trond
2012-05-28 17:07 ` Peng Tao
2012-05-28 11:26 ` Boaz Harrosh
2012-05-28 16:50 ` Peng Tao
2012-05-28 17:10 ` Boaz Harrosh
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=4FC358CA.2090301@panasas.com \
--to=bharrosh@panasas.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bergwolf@gmail.com \
--cc=linux-nfs@vger.kernel.org \
--cc=tao.peng@emc.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 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).