All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mingming <cmm@us.ibm.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Andreas Dilger <adilger@sun.com>,
	linux-ext4@vger.kernel.org, Eric Sandeen <esandeen@redhat.com>,
	Subrata Modak <subrata@linux.vnet.ibm.com>,
	Dave Jones <davej@redhat.com>,
	linux-fsdevel@vger.kernel.org
Subject: Re: Updated fsx.c program (fixed fallocate)
Date: Fri, 02 Oct 2009 16:26:05 -0700	[thread overview]
Message-ID: <1254525965.4095.210.camel@mingming-laptop> (raw)
In-Reply-To: <4AC6814C.7070305@redhat.com>

On Fri, 2009-10-02 at 17:40 -0500, Eric Sandeen wrote:
> Mingming wrote:
> > On Tue, 2009-09-29 at 16:39 -0600, Andreas Dilger wrote:
> >> I've done some work to merge some of the existing fsx.c mods into a
> >> single version.  Over & above the version that is in the LTP, I've
> >> included AKPM's O_DIRECT fixes (with a twist), the BSD mmap page and
> >> segfault handling, and per-write fsync.
> >>
> >> The twist for the O_DIRECT feature is that it will randomly open file
> >> descriptors with O_DIRECT, and if you use the Lustre-inspired multi-fd
> >> support (by specifying multiple pathnames for the output file) fsx will
> >> be testing buffered and O_DIRECT and mmap IO on the same file.
> >>
> >> Updated patch to have proper fallocate() handling in case glibc doesn't
> >> have this, for non-x86 architectures from MingMing Cao, based on code
> >> used by DB2.
> >>
> >> Signed-off-by: Andreas Dilger <adilger@sun.com>
> > 
> > On top of this, a little update to add O_DIRECT define.
> > 
> > Signed-off-by: Mingming Cao <cmm@us.ibm.com>
> > 
> > --- fsx.c.orig	2009-10-02 14:22:12.299565348 -0700
> > +++ fsx.c	2009-10-01 16:36:17.271593794 -0700
> > @@ -78,6 +78,10 @@
> >  
> >  #define	LOGSIZE	100000
> >  
> > +#ifndef O_DIRECT
> > +#define O_DIRECT        040000  /* direct disk access hint */
> > +#endif
> > +
> >  struct log_entry	oplog[LOGSIZE];	/* the log */
> >  int			logptr = 0;	/* current position in log */
> >  int			logcount = 0;	/* total ops */
> > 
> > 
> 
> I think that
> 
> #define _GNU_SOURCE
> 
> will pull in the glibc headers' definition rather than doing our own....
> 

Oh? that's sounds good...

I tried to replace above with 
#define _GNU_SOURCE	1

gcc complained O_DIRECT is still not defined. what did I missing?

Mingming
> -Eric
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



  reply	other threads:[~2009-10-02 23:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-26  5:25 Updated fsx.c program Andreas Dilger
2009-09-29 21:38 ` Andreas Dilger
2009-09-29 22:39   ` Updated fsx.c program (fixed fallocate) Andreas Dilger
2009-09-30  3:34     ` Eric Sandeen
2009-09-30 15:21     ` Randy Dunlap
2009-09-30 15:32       ` Eric Sandeen
2009-09-30 16:19         ` Dave Jones
2009-09-30 16:47           ` Eric Sandeen
2009-10-02 22:37     ` Mingming
2009-10-02 22:40       ` Eric Sandeen
2009-10-02 23:26         ` Mingming [this message]
2009-10-03  2:40           ` Nick Dokos
2009-10-03  3:40             ` Eric Sandeen

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=1254525965.4095.210.camel@mingming-laptop \
    --to=cmm@us.ibm.com \
    --cc=adilger@sun.com \
    --cc=davej@redhat.com \
    --cc=esandeen@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=subrata@linux.vnet.ibm.com \
    /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 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.