From: Sedat Dilek <sedat.dilek@googlemail.com>
To: "Ted Ts'o" <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: ext4 patches for 2.6.37-rc1?
Date: Thu, 28 Oct 2010 08:41:56 +0200 [thread overview]
Message-ID: <AANLkTinEbCycO+RB82_aB9t6AakDT08AcTYSrzFQJS6g@mail.gmail.com> (raw)
In-Reply-To: <20101027202933.GD3194@thunk.org>
Hi Ted,
thanks for your explanations.
Just saw your GIT-pull request on LKML [1] and compiling now
linux-next (next-20101028) [2] which includes ext4.
Linus pulled to upstream, so 2.6.36-git11 will have the ext4-patches :-).
Thanks all for their work on ext4!
Kind Regards,
- Sedat -
[1] http://lkml.org/lkml/2010/10/28/12
[2] http://lkml.org/lkml/2010/10/27/509
On Wed, Oct 27, 2010 at 10:29 PM, Ted Ts'o <tytso@mit.edu> wrote:
> On Wed, Oct 27, 2010 at 12:36:46PM +0200, Sedat Dilek wrote:
>>
>> I was wondering if Ted will send ext4 patches within the open
>> merge-window for 2.6.37-rc1.
>
> Yes, I am planning on sending patches to Linus.
>
> It's a bit late because I've been crazy busy this past few weeks.
>
>> If you plan to send to Linus, can you give a short overview what
>> endusers will expect?
>
> lazy inode table init, improved scalability for buffered writeback (3x
> throughput improvement when writing large files in parallel on 48 and
> 192 threads on a 48-core machine), and a bunch of cleanups and bug
> fixes.
>
>> BTW, in which of the GIT trees ([1], [2]) is the ext4 development
>> actually happening?
>>
>> [1] http://git.kernel.org/?p=linux/kernel/git/tytso/ext4.git;a=summary
>> [2] http://repo.or.cz/w/ext4-patch-queue.git
>
> Primary development happens in [2], and then it gets mirrored to [1]
> periodically.
>
> - Ted
>
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-10-28 6:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 10:36 ext4 patches for 2.6.37-rc1? Sedat Dilek
2010-10-27 20:29 ` Ted Ts'o
2010-10-28 6:41 ` Sedat Dilek [this message]
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=AANLkTinEbCycO+RB82_aB9t6AakDT08AcTYSrzFQJS6g@mail.gmail.com \
--to=sedat.dilek@googlemail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=tytso@mit.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).