From: Christoph Hellwig <hch@infradead.org>
To: NeilBrown <neilb@cse.unsw.edu.au>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
nfs@lists.sourceforge.net
Subject: Re: [PATCH kNFSd 4 of 4] Use llseek instead of f_pos= for directory seeking.
Date: Mon, 16 Aug 2004 10:23:02 +0100 [thread overview]
Message-ID: <20040816102302.B9177@infradead.org> (raw)
In-Reply-To: <20040816102102.A9177@infradead.org>; from hch@infradead.org on Mon, Aug 16, 2004 at 10:21:02AM +0100
On Mon, Aug 16, 2004 at 10:21:02AM +0100, Christoph Hellwig wrote:
> > So instead, we use 'llseek' copied out of fs/read_write.c
> > use that, both to seek at the start, and the find the new position at
> > the end.
>
> llseek from fs/read_write.c has been renamed to vfs_llseek and you can
> just use it now.
Sorry for the noise, I see this is 2.4. But I think the 2.6 variant would be
preferable for 2.4 aswell.
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-08-16 9:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-16 3:58 [PATCH kNFSd 0 of 4] Introduction NeilBrown
2004-08-16 3:58 ` [PATCH kNFSd 4 of 4] Use llseek instead of f_pos= for directory seeking NeilBrown
2004-08-16 9:21 ` Christoph Hellwig
2004-08-16 9:23 ` Christoph Hellwig [this message]
2004-08-16 3:58 ` [PATCH kNFSd 1 of 4] Fixed possibly xdr parsing error if write size exceed 2^31 NeilBrown
2005-07-11 9:50 ` Olaf Kirch
2005-07-12 6:42 ` Marcelo Tosatti
2004-08-16 3:58 ` [PATCH kNFSd 3 of 4] Allow larger NFSd MAXBLKSIZE on architectures with larger PAGE_SIZE NeilBrown
2004-08-16 3:58 ` [PATCH kNFSd 2 of 4] mark NFS/TCP not EXPERIMENTAL NeilBrown
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=20040816102302.B9177@infradead.org \
--to=hch@infradead.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs@lists.sourceforge.net \
/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