| To: | Federico Sevilla III <jijo@xxxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: XFS and preemptive kernel patch |
| From: | Anuradha Ratnaweera <anuradha@xxxxxxx> |
| Date: | Sat, 10 Nov 2001 10:45:54 +0600 |
| Cc: | Linux XFS Mailing List <linux-xfs@xxxxxxxxxxx> |
| In-reply-to: | <Pine.LNX.4.40.0111101232210.19755-100000@xxxxxxxxxxxxxxxxxxxxxxxxx>; from jijo@xxxxxxxxxxxxxxxxxxxx on Sat, Nov 10, 2001 at 12:37:26PM +0800 |
| References: | <20011110102710.A2703@xxxxxx> <Pine.LNX.4.40.0111101232210.19755-100000@xxxxxxxxxxxxxxxxxxxxxxxxx> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5i |
On Sat, Nov 10, 2001 at 12:37:26PM +0800, Federico Sevilla III wrote:
>
> On Sat, 10 Nov 2001 at 10:27, Anuradha Ratnaweera wrote:
>
> > Do you mean XFS code can be preemptible at _kernel_ space?
>
> I'm not sure, either. As far as I remember the XFS code (kernel space) was
> modified to be preemptible. Exactly what gets preempted is beyond me. I hope
> the XFS gurus can help us out with this (maybe this is worth a FAQ entry,
> Seth?). :)
When I recently raised the question of XFS not being in the mainstream kernel,
it was told that it is touching too much kernel internals, some of which are
2.5 stuff. May be this is one... Any clue?
Regards,
Anuradha
--
Debian GNU/Linux (kernel 2.4.13)
Make it idiot-proof, and someone will breed a better idiot.
-- Oliver Elphick
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS and preemptive kernel patch, Federico Sevilla III |
|---|---|
| Next by Date: | TAKE - xfsrestore - allow 255 char pathnames, Timothy Shimmin |
| Previous by Thread: | Re: XFS and preemptive kernel patch, Federico Sevilla III |
| Next by Thread: | Re: XFS and preemptive kernel patch, Steve Lord |
| Indexes: | [Date] [Thread] [Top] [All Lists] |