All of lore.kernel.org
 help / color / mirror / Atom feed
From: hujianyang <hujianyang@huawei.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-unionfs@vger.kernel.org
Subject: Re: [PATCH] ovl: Cleanup redundant blank lines
Date: Wed, 26 Nov 2014 17:07:12 +0800	[thread overview]
Message-ID: <54759840.3050101@huawei.com> (raw)
In-Reply-To: <54758C7B.6040402@huawei.com>

Hi Miklos,

Will you apply my previous patch "ovl: Use macros to present
ovl_xattr"? These two patches(previous one and this one) are
based on branch *overlayfs-current* and conflict with each
other.

I don't know which branch I should use, overlayfs-current or
overlayfs-next. How could I join the development?


By the way, do you think we can make use of "kmem_cache" to
manage "struct ovl_entry"? I think it will speedup operations
like *ls*. I saw your work about multi-layer support. The size
of "struct ovl_entry" will be variable. In addition, some free
paths of ovl_entry rely on RCU. So maybe it's not easy.


Thanks~!

Hu


  reply	other threads:[~2014-11-26  9:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-26  8:16 [PATCH] ovl: Cleanup redundant blank lines hujianyang
2014-11-26  9:07 ` hujianyang [this message]
2014-11-26  9:16   ` Miklos Szeredi

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=54759840.3050101@huawei.com \
    --to=hujianyang@huawei.com \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    /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.