From: Jan Kara <jack@suse.cz>
To: Namjae Jeon <linkinjeon@gmail.com>
Cc: Jan Kara <jack@suse.cz>,
linux-kernel@vger.kernel.org,
Namjae Jeon <namjae.jeon@samsung.com>,
Ashish Sangwan <a.sangwan@samsung.com>
Subject: Re: [PATCH 5/6] udf: implement extent caching while reading-writing to a file
Date: Thu, 10 Jan 2013 17:59:42 +0100 [thread overview]
Message-ID: <20130110165942.GA30000@quack.suse.cz> (raw)
In-Reply-To: <CAKYAXd-Mm72cGwAoYd1ZtMFXD8WF2E3u7S23zckhoFA=h+4XhA@mail.gmail.com>
On Wed 09-01-13 15:26:43, Namjae Jeon wrote:
> 2012/12/13, Namjae Jeon <linkinjeon@gmail.com>:
> > 2012/10/19, Namjae Jeon <linkinjeon@gmail.com>:
> >> 2012/10/19, Jan Kara <jack@suse.cz>:
> >>> Hello,
> >>>
> >>> On Wed 10-10-12 00:10:01, Namjae Jeon wrote:
> >>>> From: Namjae Jeon <namjae.jeon@samsung.com>
> >>>>
> >>>> This patch implements extent caching.
> >>>> Instead of reading metadata everytime from file's starting position,
> >>>> now we read from the cached extent.
> >>>> This speeds up the transformation of file logical offsets to
> >>>> corresponding on-disk blocks.
> >>> I have some mostly minor comments to the patch. But when reading the
> >>> extent code it is just ugly and hard to follow. So I'm thinking how to
> >>> improve that before making things even harder with the extent cache. So
> >>> give me a few more days please.
> >> Hi Jan.
> >> Okay, I see. Thanks!
> >>>
> > Hi Jan.
> > Sorry for interrupt. I am still waiting for your review.
> > Would you check extent cache patches ?
> > Thanks.
> Hi Jan.
>
> Maybe You think you didn't convince extent cache implementation of
> write part in this patch.
> So I suggest that once, we add extent cache of read part first in case
> of read-only mount type.
> because it is real issue on 3D BD-disk playing(BD Disk is used on
> read-only mount type).
> And I will check more write part again.
I'm sorry for not getting to you earlier. Yes, support for reading should
be easy enough and we can add support for write when I finish the extent
cleanup (I already have the new code written but I need to integrate it
with the rest of UDF code...). Can you please send the patch for read
support and I'll queue it for the next merge window? Thanks!
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2013-01-10 16:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 15:10 Namjae Jeon
2012-10-18 22:30 ` Jan Kara
2012-10-19 4:48 ` Namjae Jeon
2012-12-13 2:10 ` Namjae Jeon
2013-01-09 6:26 ` Namjae Jeon
2013-01-10 16:59 ` Jan Kara [this message]
2013-01-11 0:49 ` Namjae Jeon
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=20130110165942.GA30000@quack.suse.cz \
--to=jack@suse.cz \
--cc=a.sangwan@samsung.com \
--cc=linkinjeon@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namjae.jeon@samsung.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
all inboxes | Powered by JetHome®