From: Wengang Wang <wen.gang.wang@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 1/1] OCFS2: fasten dlm_lock_resource hash_table lookups
Date: Thu, 23 Apr 2009 19:06:46 +0800 [thread overview]
Message-ID: <49F04BC6.5040206@oracle.com> (raw)
In-Reply-To: <49EFD1F9.1020009@oracle.com>
Hi Sunil,
Sunil Mushran wrote:
> Wengang,
>
> When we backport, we like to add bread crumbs so that we can track back
> to the original patch. This helps us in cases where we, say, forget to
> include a patch. Also, we want to retain original authorship.
>
> For example:
> http://oss.oracle.com/git/?p=ocfs2-1.4.git;a=commitdiff;h=174f54db9af7c67a1afaa947aed934b9c80f588c
>
>
> So don't merge the patches. Add the mainline commit at the top of the
> patch. As 1.2 is svn, ensure the authors name is included in an
> Authored-by
> tag.
>
Ok, I will follow that for later backports.
> Has it been tested in 1.2?
>
No. Since I think this part(hash_table
construction/insertions/lookups/destruction) is independent and no
changes from the original patch,
I didn't test it --only made sure it pass compilation.
well, you want to test the functionility(correctness) or the performance?
thanks,
wengang.
> Thanks
> Sunil
>
> wengang wang wrote:
>> #backporting the 3 patches at
>> http://kernel.us.oracle.com/~smushran/srini/ to 1.2.
>>
>> enlarge hash_table capacity to fasten hash_table lookups.
>>
>
prev parent reply other threads:[~2009-04-23 11:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 6:04 [Ocfs2-devel] [PATCH 1/1] OCFS2: fasten dlm_lock_resource hash_table lookups wengang wang
2009-04-23 2:27 ` Sunil Mushran
2009-04-23 11:06 ` Wengang Wang [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=49F04BC6.5040206@oracle.com \
--to=wen.gang.wang@oracle.com \
--cc=ocfs2-devel@oss.oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.