[Top] [All Lists]

Re: TAKE 981498 - Use KM_NOFS for debug trace buffers

To: Bhagi rathi <jahnu77@xxxxxxxxx>
Subject: Re: TAKE 981498 - Use KM_NOFS for debug trace buffers
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Mon, 11 Aug 2008 17:58:55 +1000
Cc: Lachlan McIlroy <lachlan@xxxxxxx>, xfs@xxxxxxxxxxx
In-reply-to: <cc7060690808072216q29efacf4tdf363fe3ed8a2c44@xxxxxxxxxxxxxx>
Mail-followup-to: Bhagi rathi <jahnu77@xxxxxxxxx>, Lachlan McIlroy <lachlan@xxxxxxx>, xfs@xxxxxxxxxxx
References: <20080806061553.A8D8958C52A4@xxxxxxxxxxxxxxxxxxxxxxx> <cc7060690808061012x43511581m15c794e72129becc@xxxxxxxxxxxxxx> <20080806201957.GQ21635@disturbed> <cc7060690808071043r659aea9fn4e28959b3a62081e@xxxxxxxxxxxxxx> <cc7060690808072216q29efacf4tdf363fe3ed8a2c44@xxxxxxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Fri, Aug 08, 2008 at 10:46:56AM +0530, Bhagi rathi wrote:
> >  Are we safe that we fixed all these real problems by looking
> >  into possible allocations that will enter into file-system? The
> >  problem with trace buffers is telling us to clean this code path.
> >
> >  By the way, I browse the source code from lxr.linux.no.
> >  If I have to browse the latest xfs source code with linux
> >  kernel that is used at SGI, how can I do that?
> >
>  Any pointers on this? I wish to setup my own xfs development enviroment
>  and details on this will be helpful.

Well, you could look at the XFS home page and follow the links to:

Or for just the kernel source you can use the master branch
of the XFS git tree at:

git://oss.sgi.com:8090/xfs/xfs-2.6.git master


Dave Chinner

<Prev in Thread] Current Thread [Next in Thread>