From: Hareesh Nagarajan <hareesh@google.com>
To: dipankar@in.ibm.com
Cc: Greg KH <greg@kroah.com>, linux-kernel@vger.kernel.org
Subject: Re: Porting kref to a 2.4 kernel (2.4.20 or greater)
Date: Thu, 16 Jun 2005 09:45:26 -0700 [thread overview]
Message-ID: <42B1ACA6.7020105@google.com> (raw)
In-Reply-To: <20050616091853.GA4965@in.ibm.com>
Dipankar Sarma wrote:
> On Wed, Jun 15, 2005 at 03:47:51PM -0700, Hareesh Nagarajan wrote:
>
>>Correction:
>>(Appears with a *)
>>
>>Greg KH wrote:
>>
>>>On Wed, Jun 15, 2005 at 10:20:04AM -0700, Hareesh Nagarajan wrote:
>>>
>>>
>>>>What stumbling blocks do you think I would encounter if I wanted to port
>>>>kref to a 2.4.xx kernel? Is kref tightly coupled with the kernel object
>>>>infrastructure found in the 2.6.xx kernel?
>>>
>>>Have you looked at the kref code to see if there is any such coupling?
>>
>>>Can you describe any problems you are having doing the uncoupling?
>>
>>I'm having problems porting the KObject* and Work Queue infrastructure
>>to the 2.4 kernel. Any ideas if anyone has tried this port?
>>
>>(Correction: * => I meant KThread)
>
>
> There were a number of backports of 2.6 workqueue stuff without
> kthread (before they were introduced for cpu hotplug) floating
> around in mailing list. You can probably google for them.
I will do that!
> Aren't they sufficient or does google want to do CPU hotplug ? :)
I was thinking of porting the RelayFS patches (from 2.6.11-mm2) to the
2.4 kernel. RelayFS seems to use the work queue infrastructure.
And AFAIK, Google doesn't seem to be too interested in hotplugging :)
Thanks Dipankar!
Hareesh
next prev parent reply other threads:[~2005-06-16 16:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-15 17:20 Porting kref to a 2.4 kernel (2.4.20 or greater) Hareesh Nagarajan
2005-06-15 22:07 ` Greg KH
2005-06-15 22:38 ` Hareesh Nagarajan
2005-06-15 22:47 ` Hareesh Nagarajan
2005-06-16 9:18 ` Dipankar Sarma
2005-06-16 16:45 ` Hareesh Nagarajan [this message]
2005-06-16 18:34 ` Greg KH
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=42B1ACA6.7020105@google.com \
--to=hareesh@google.com \
--cc=dipankar@in.ibm.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
/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