* Re: [ceph-users] Backporting the kernel client
[not found] <alpine.DEB.2.02.1304291544340.23141@orbit.lan>
@ 2013-04-29 14:29 ` Yehuda Sadeh
2013-04-29 15:05 ` James Page
0 siblings, 1 reply; 2+ messages in thread
From: Yehuda Sadeh @ 2013-04-29 14:29 UTC (permalink / raw)
To: Juha Aatrokoski, ceph-devel; +Cc: ceph-users@lists.ceph.com
On Mon, Apr 29, 2013 at 6:16 AM, Juha Aatrokoski <jha@kurp.hut.fi> wrote:
> I'm probably not the only one who would like to run a distribution-provided
> kernel (which for Debian Wheezy/Ubuntu Precise is 3.2) and still have a
> recent-enough Ceph kernel client. So I'm wondering whether it's feasible to
> backport the kernel client to an earlier kernel. The plan is as follows:
>
> 1) Grab the Ceph files from https://github.com/ceph/ceph-client (and put
> them over the older kernel sources). If I got it right the files are:
> include/keys/ceph-type.h include/linux/ceph/* fs/ceph/* net/ceph/*
> drivers/block/rbd.c drivers/block/rbd_types.h
>
> 2) Make (trivial) adjustments to the source code to account for changed
> kernel interfaces.
>
> 3) Compile as modules and install the new Ceph modules under /lib/modules.
>
> 4) Reboot to a standard distribution kernel with up-to-date Ceph client.
>
>
> Now the main questions are:
>
> Q1: Is the Ceph client contained in the files mentioned in 1), or does it
> include changes elsewhere in the kernel that cannot be built as modules?
The ceph stuff is mostly there, if you exclude make file changes.
Don't think there's anything outside.
>
> Q2: Regarding 2), are there any nontrivial interface changes i.e. Ceph
> actually using newly introduced features instead of just adapting to a
> changed syntax?
I don't really know, haven't been actively looking at the kernel side
for a while. It used to compile on that kernel version, so you can
always refer to the older version and see how it used to work. Usually
you can just try to compile it, see where it fails and then try to
figure out what has changed there.
Yehuda
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [ceph-users] Backporting the kernel client
2013-04-29 14:29 ` [ceph-users] Backporting the kernel client Yehuda Sadeh
@ 2013-04-29 15:05 ` James Page
0 siblings, 0 replies; 2+ messages in thread
From: James Page @ 2013-04-29 15:05 UTC (permalink / raw)
To: Yehuda Sadeh; +Cc: Juha Aatrokoski, ceph-devel, ceph-users@lists.ceph.com
Hi Juha
On 29/04/13 15:29, Yehuda Sadeh wrote:
> On Mon, Apr 29, 2013 at 6:16 AM, Juha Aatrokoski<jha@kurp.hut.fi> wrote:
>> >I'm probably not the only one who would like to run a distribution-provided
>> >kernel (which for Debian Wheezy/Ubuntu Precise is 3.2) and still have a
>> >recent-enough Ceph kernel client. So I'm wondering whether it's feasible to
>> >backport the kernel client to an earlier kernel. The plan is as follows:
Ubuntu 12.04 now includes Hardware Enablement Kernels from Quantal (3.5)
and soon from Raring (3.8):
http://www.jorgecastro.org/2013/02/19/what-the-lts-enablement-stack-means-for-sysadmins/
This allows you to use a more recent, distro provided kernel than 3.2
which should have the required fixes/features you need.
That said if you are having problems with the 3.2 kernel please do
report bugs back to Ubuntu.
Cheers
James
--
James Page
Technical Lead
Ubuntu Server Team
james.page@canonical.com
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-04-29 15:05 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <alpine.DEB.2.02.1304291544340.23141@orbit.lan>
2013-04-29 14:29 ` [ceph-users] Backporting the kernel client Yehuda Sadeh
2013-04-29 15:05 ` James Page
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.