Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fusionio.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: How are userspace & kernelspace kept in sync?
Date: Fri, 5 Apr 2013 20:20:27 -0400	[thread overview]
Message-ID: <20130406002027.GS1876@localhost.localdomain> (raw)
In-Reply-To: <515F54D8.4050903@redhat.com>

On Fri, Apr 05, 2013 at 04:48:56PM -0600, Eric Sandeen wrote:
> One thing led to another in poking around the code, and I realized
> that while userspace has lots of code copied from the kernel, it
> was last copied in 2008, in many cases.  ;)
> 
> What's the plan here, how are userspace & kernelspace to be kept
> in sync?
> 
> New features fairly obviously hit both, but what about bugfixes
> that hit one codebase or the other?
> 
> Is it clear (to anyone) which code needs to be synced?
> 
> Should it be done as a wholesale sync-up/rebase from time to
> time, or should commits be merged from one to the other?
>

So having just had to bring back part of the free space cache code I'd say we
just cherry pick stuff since it is a huge pain to just copy it over, especially
when you start talking about the extent buffer stuff.  If maybe we could
seperate out the really kernel specific stuff (like the stuff that does the
reading/writing or interfaces with vfs) and the btrfs specific stuff then maybe
it would be good to keep them in sync.  But honestly I think the core stuff is
pretty solid right now so cherry-picking is probably our better bet.  Thanks,

Josef 

  reply	other threads:[~2013-04-06  0:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-05 22:48 How are userspace & kernelspace kept in sync? Eric Sandeen
2013-04-06  0:20 ` Josef Bacik [this message]
2013-04-06  0:34   ` Eric Sandeen

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=20130406002027.GS1876@localhost.localdomain \
    --to=jbacik@fusionio.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=sandeen@redhat.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