| To: | utz lehmann <xfs@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH] Re: Reduce XFS footprint (was Re: TAKE - remove a function xfs added to filemap.c |
| From: | Eric Sandeen <sandeen@xxxxxxx> |
| Date: | 29 Jan 2002 14:09:53 -0600 |
| Cc: | Andi Kleen <ak@xxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <20020129205653.A13502@xxxxxxxxxx> |
| References: | <200201291751.g0THp897004750@xxxxxxxxxxxxxx> <20020129194001.A16401@xxxxxxxxxxxxx> <20020129202509.A31370@xxxxxxxxxxxxx> <20020129205653.A13502@xxxxxxxxxx> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
On Tue, 2002-01-29 at 13:56, utz lehmann wrote: > Hi > > I have a few questions. > > Is xfs using less 64bit arithmetics when compiled without > XFS_BIG_FILESYSTEMS and/or XFS_BIG_FILES? I think this will save some cpu > cyles on x86. I have this same question, I'll do some benchmarking to find out. > What happends with old files larger than 2GB, when a kernel without > XFS_BIG_FILES is used? sb->s_maxbytes gets set to a smaller value, so all the normal kernel size checks kick in, and you won't be able to seek/truncate/read/write past the smaller value. -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@xxxxxxx SGI, Inc. |
| Previous by Date: | Re: [PATCH] Re: Reduce XFS footprint (was Re: TAKE - remove a function xfs added to filemap.c, utz lehmann |
|---|---|
| Next by Date: | Re: [PATCH] Re: Reduce XFS footprint (was Re: TAKE - remove a function xfs added to filemap.c, Andi Kleen |
| Previous by Thread: | Re: [PATCH] Re: Reduce XFS footprint (was Re: TAKE - remove a function xfs added to filemap.c, utz lehmann |
| Next by Thread: | Excellent job SGI, henka |
| Indexes: | [Date] [Thread] [Top] [All Lists] |